Hi
1.- I want to install a new Rom (Android 4.4.2 KitKat omniROM)
2.- But first I need to install TWRP (.blob), so I need to install and run a fastboot tool (Minimal adb/fastboot tool)
I unlocked the bootloader of the tablet
I install the fastboot
I install the drivers of the fastboot of the Asus
I copy the file.blob to the same folder of the fastboot
I open the fastboot and in the CMD I wrote ''fastboot devices'' and it find the Asus so in the screen was numers and letters like a code...but then I wrote the command Fastboot -i 0x0B05 flash recovery file.blob but then give an error (failed....(no such device or address))
I tried all to solve this problem but I cant.. so I need your help.
I tried:
■Reinstall fastboot tool
■Restart the tablet
■Use all the usb ports of the PC
■Reinstall drivers
■Used apps like SDK Manager
■Used other usb cable
luisldu said:
Hi
1.- I want to install a new Rom (Android 4.4.2 KitKat omniROM)
2.- But first I need to install TWRP (.blob), so I need to install and run a fastboot tool (Minimal adb/fastboot tool)
I unlocked the bootloader of the tablet
I install the fastboot
I install the drivers of the fastboot of the Asus
I copy the file.blob to the same folder of the fastboot
I open the fastboot and in the CMD I wrote ''fastboot devices'' and it find the Asus so in the screen was numers and letters like a code...but then I wrote the command Fastboot -i 0x0B05 flash recovery file.blob but then give an error (failed....(no such device or address))
I tried all to solve this problem but I cant.. so I need your help.
I tried:
■Reinstall fastboot tool
■Restart the tablet
■Use all the usb ports of the PC
■Reinstall drivers
■Used apps like SDK Manager
■Used other usb cable
Click to expand...
Click to collapse
Is your bootloader unlocked?
Edit: wait I read the op and it says you did unlock it..
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
I'd say try to use a completely different USB or computer. If that doesn't work, you can actually flash it from the system itself if you have root. Can't remember the command. Give me a second.
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Are you on 4.2 bootloader?
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:39 PM ---------- Previous post was at 07:31 PM ----------
To install without using fastboot, download twrp, make sure its one of the newer twrps, I think 2.7 and above is required for KitKat, and..
[QUOTE/] Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.blob
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot to complete installation.
[/QUOTE]
Sent from my SM-N900T using XDA Free mobile app
Problem Solved!
andrewnelson23 said:
Is your bootloader unlocked?
Edit: wait I read the op and it says you did unlock it..
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
I'd say try to use a completely different USB or computer. If that doesn't work, you can actually flash it from the system itself if you have root. Can't remember the command. Give me a second.
Sent from my SM-N900T using XDA Free mobile app
---------- Post added at 07:31 PM ---------- Previous post was at 07:28 PM ----------
Are you on 4.2 bootloader?
Click to expand...
Click to collapse
So, yesterday I clean the Asus Cable, the port of the pc and the port of tablet and finally works, so I flashed my tablet with TWRP recovery and the 4.4.4 omniROM Nightly.
The all problem was the cable and the ports.
:good:
Related
I'm a little confused on how to do this. I want to flash an RUU as my phone is spazzing out, constant freeze and reboot, it has even done it in fastboot and in recovery. I dont know that an RUU will help, but Im low on options and I just want to try it.
Anyway, when I unlocked the bootloader the first time, I used a script - consequently, I dont know how to get to adb. I am not sure I actually have adb on my computer, as I dont completely understand how the script worked. If I go to the command prompt and try to open adb the way certain tutorials say to do, I can't find it.
Any advice, or a pointer to a good tutorial would be much appreciated.
This is the very reason I hate 1-clicks
Here ya go tho:beer:
Ok download this zip- http://db.tt/5ePa4XV5
Go create a folder on the root of your main hard drive (C:/) named "android".
Unzip the download and stick all the files in it from that folder.
Open up a command prompt and type
cd\
cd c:/android
Now plug in phone booted up, with USB debugging enabled in settings>developer options
Type-
adb devices
Should see devices serial# pop up
Type
adb reboot bootloader
Once bootloader loads up, in red you'll see fastboot usb.
Type
fastboot oem lock
Now your relocked, don't touch the phones just run the ruu. Make sure you run the same ruu version of your phones firmware version
Done
Sent from my HTC One X+ p_type 0.91.0
Thank you! Now hopefully I can get it to boot up again, as it's now stopped responding. I had it all the way to the main screen earlier, but now it's being poopy again.
hcricket said:
Thank you! Now hopefully I can get it to boot up again, as it's now stopped responding. I had it all the way to the main screen earlier, but now it's being poopy again.
Click to expand...
Click to collapse
Went back and saw your older posts......u got bigger problems.........u need to get it booted all the way up........instructions coming....
Sent from my HTC One X+ p_type 0.91.0
---------- Post added at 03:27 AM ---------- Previous post was at 02:59 AM ----------
Verify you have hboot 1.09 on device before following this.......
1. Download this and stick in your adb folder, the android folder u created- http://db.tt/TBXnYXEW
2. Open up your cmd window and cd to adb folder
cd\
cd c:/android
3. Push Hboot file to sdcard-
adb push hboot109.img /sdcard/hboot109.img
4. Get a shell with root permissions-
adb shell
su
5. send signed hboot to proper partition-
dd if=/sdcard/hboot109.img of=/dev/block/mmcblk0p12
6. Once it's done, resend it-
dd if=/sdcard/hboot109.img of=/dev/block/mmcblk0p12
7. Exit out of shell, type-
exit
exit
adb reboot bootloader
8.wait for bootloader to start and then download-
http://db.tt/sXmdepmX
Stick it in your android folder.
9. Back to cmd prompt, make sure your in the /android directory (ref. step 2), type-
fastboot flash recovery twrp.img
10. Again-
fastboot flash recovery twrp.img
11. On your phone, select bootloader, then recovery.
Should boot up into twrp recovery, do a full wipe of cache, dalvik cache, system, factory reset, then flash your Rom of choice for the evita one xl.
Sent from my HTC One X+ p_type 0.91.0
18th.abn said:
Went back and saw your older posts......u got bigger problems.........u need to get it booted all the way up........instructions coming....
Sent from my HTC One X+ p_type 0.91.0
---------- Post added at 03:27 AM ---------- Previous post was at 02:59 AM ----------
Verify you have hboot 1.09 on device before following this.......
1. Download this and stick in your adb folder, the android folder u created- http://db.tt/TBXnYXEW
2. Open up your cmd window and cd to adb folder
cd\
cd c:/android
3. Push Hboot file to sdcard-
adb push hboot109.img /sdcard/hboot109.img
4. Get a shell with root permissions-
adb shell
su
5. send signed hboot to proper partition-
dd if=/sdcard/hboot109.img of=/dev/block/mmcblk0p12
6. Once it's done, resend it-
dd if=/sdcard/hboot109.img of=/dev/block/mmcblk0p12
7. Exit out of shell, type-
exit
exit
adb reboot bootloader
8.wait for bootloader to start and then download-
http://db.tt/sXmdepmX
Stick it in your android folder.
9. Back to cmd prompt, make sure your in the /android directory (ref. step 2), type-
fastboot flash recovery twrp.img
10. Again-
fastboot flash recovery twrp.img
11. On your phone, select bootloader, then recovery.
Should boot up into twrp recovery, do a full wipe of cache, dalvik cache, system, factory reset, then flash your Rom of choice for the evita one xl.
Sent from my HTC One X+ p_type 0.91.0
Click to expand...
Click to collapse
Thank you, I can't wait to try this after work. However, when I plug in my phone now, nothing happens at all... It doesnt even show up in device manager.
Okay, I took it to work and plugged it in to my USB, and the battery light came on after a while, so I have hope that I will be able to boot at some point. Couple questions though:
1. Will I need to get to the settings and get to USB debugging first, or can I just mount the SD card in TWRP?
2. How do I tell if I have hboot 1.09?
Currently, in my Android folder, I have a folder called adb_fb_files. In that folder, I have:
adb
adbwinapi.dll
adbwinusbapi.dll
aruglobal.dll
fastboot
hboot109.img
You need to unzip the adb_files I had you download.....the files inside of it are what go into your adb folder, not the adb_files.zip itself......
Sent from my HTC One X using xda premium
---------- Post added at 09:06 PM ---------- Previous post was at 08:58 PM ----------
If your on firmware 1.85, or 1.73 you have hboot 1.09............
You can do the steps from twrp recovery.....but don't mount usb, once twrp is booted you can simply open a cmd prompt, cd to your adb folder and type
adb push hboot109.img /sdcard/hboot109.img
adb shell
dd if=/sdcard/hboot109.img of=/dev/block/mmcblk0p12
then press up arrow, then enter to repeat command
Once it's done, in twrp select reboot>bootloader
From there, reflash your recovery, then boot recovery, wipe your cache, dalvik, factory reset, system......flash new evita one x rom
Sent from my HTC One X using xda premium
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
I'll send a pm to my gtalk...if you get into twrp, and wanna download teamviewer on your pc for free, I'll remote in and get u fixed up from here
Sent from my HTC One X using xda premium
This is work for other device to sir?
Hello guys,
Sorry if this is redundant but I did search before making this post so feel free to edit or remove moderators.
I had root prior to last update 7.5.1. Lost root and I could not re-root using Qemu/Root Many/KFAide and I spent a lot of time playing with the CMD prompts. So I was curious and tried Root Master 1.3.6. Sure enough it worked for me in 1 MINUTE!!! So I am only posting this in case there are others out there like me. I found this post to be helpful since it had a lot of pics so I will not put up my own pictures:
http://forum.xda-developers.com/showthread.php?t=2783447
Otherwise, the my cliff notes of the install is:
Copy/transfer Root_Master_1-3-6.apk to any folder on Kindle via usb cable (assuming you installed drivers already, if not search forum)
Install/Open
Select Mulai Root
Popup with two choices will appear Root/Batal (cancel): Select Root
Another popup will show strange characters/Batal: Select Batal this time
You're Done!
Last step: Clean up by going to apps and press/hold root master to remove from device (it's no longer needed since you are rooted and I read it may contain some kind of script that sends your device information to someone bored, however the root itself is safe - I hope!)
Also, four common terms you'll see when you open apps that asks for root permission not covered in the thread above:
jangan tanya lagi - do not ask again
Perizinan - Allow
Tolak - reject
di izinkan xxxxxxxxxxxx dapatkan izin - authorized xxxxxxxxxxxx to get "root" permission (xxx is the name of the app you are opening)
I will post up my version of the file I've used but I believe the file in the thread above is also identical.
Thanks to all and this forum,
Nano out
P.S. Another solution working to removing the Special Offers Lockscreen Ads is to freeze it with Titanium Backup ($$) or ROM Toolbox Lite (free) both can be found on the Google Play Store:
For ROM Toolbox Lite: Open after install, select app manager, click on Kindle Special Offers, select Freeze, then Yes. I'm unsure what the advanced freeze is but my ads are gone and still gone after reboot so I'm a happy camper.
i also have 7.5.1 but stock. never been rooted. i downloaded this APK and followed the instructions... but it didn't successfully root it for me. so... now there's like a Perizinan rumah tangga app that i can't get rid in the app store.... so i'm factory resetting everything again hahaha i think it's malware
---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------
this is great, this malware has survived a factory reset.... thanks a lot
JediFonger said:
i also have 7.5.1 but stock. never been rooted. i downloaded this APK and followed the instructions... but it didn't successfully root it for me. so... now there's like a Perizinan rumah tangga app that i can't get rid in the app store.... so i'm factory resetting everything again hahaha i think it's malware
---------- Post added at 12:29 AM ---------- Previous post was at 12:17 AM ----------
this is great, this malware has survived a factory reset.... thanks a lot
Click to expand...
Click to collapse
follow the unrooting part mentioned in this guide:
http://forum.xda-developers.com/showthread.php?t=2783447
this is the best method of rooting on 7.5.1:
http://akauntu.blogspot.com/2014/12/install-custom-rom-on-amazon-kindle_26.html
so i did follow both, the first link didn't do anything but load an app and hten it loaded an app that wouldn't go away even after factory reset. great.
secondly, i used the 'best method of rooting on 7.5.1' and the only difference i saw was using non-admin to run commandlines so that made some differences. but i'm not i still have root. the major issue is i can't reboot into fastboot... so that defeats the purpose since i can't downgrade to 7.2.3, which is needed to proceed.
any other tips?
according to a few root checker apps. i have root... but i just can't reboot into fastboot
lolwatpear said:
follow the unrooting part mentioned in this guide:
http://forum.xda-developers.com/showthread.php?t=2783447
this is the best method of rooting on 7.5.1:
http://akauntu.blogspot.com/2014/12/install-custom-rom-on-amazon-kindle_26.html
Click to expand...
Click to collapse
JediFonger said:
so i did follow both, the first link didn't do anything but load an app and hten it loaded an app that wouldn't go away even after factory reset. great.
secondly, i used the 'best method of rooting on 7.5.1' and the only difference i saw was using non-admin to run commandlines so that made some differences. but i'm not i still have root. the major issue is i can't reboot into fastboot... so that defeats the purpose since i can't downgrade to 7.2.3, which is needed to proceed.
any other tips?
according to a few root checker apps. i have root... but i just can't reboot into fastboot
Click to expand...
Click to collapse
The first link I posted was to remove that app installed from root master where is says unrooting and "1.Open "Perizinan rumah tangga."
As for the second link, you should follow the youtube videos as well as some of the info isn't mentioned in the text. You need to make sure the kindle fire drivers are installed properly when using adb and fastboot. One time they were fine for me for adb, but when I went into fastboot, they weren't properly installed. So, I uninstalled them in the device manager and replugged in the kindle and they worked properly.
But since root checker apps are saying you have root, adb shell su -c "reboot bootloader" should get you into fastboot mode. Then you run that other tool to downgrade.
when i run that command i get connection io timer error and thats it. it will only reboot into recovery but never fastboot. i'm tryjng to make or acquire a fastboot cable. the original kindle usb cable is a fastboot cable right? i have to find it not sure where i stored it
---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------
i dont have any other issues adb driverd and cmd run fine i just cannot get into fastboot no matter what i have used
JediFonger said:
when i run that command i get connection io timer error and thats it. it will only reboot into recovery but never fastboot. i'm tryjng to make or acquire a fastboot cable. the original kindle usb cable is a fastboot cable right? i have to find it not sure where i stored it
---------- Post added at 09:04 PM ---------- Previous post was at 09:02 PM ----------
i dont have any other issues adb driverd and cmd run fine i just cannot get into fastboot no matter what i have used
Click to expand...
Click to collapse
you don't need a fastboot cable for that method. I don't have one myself and have no issue.
when you do "adb devices", does a serial come up?
yes i can run adb devices no problem. i know how to adb kill-server and restart the devices as well so it is detected. i have drivers properly installed as a ADB device under device manager. i can adb reboot and even adb reboot recovery but i can't run adb reboot-bootloader or adb reboot bootloader
and adb shell gets me non-su user prompt but i can't su into the root access #. when i run adb shell su -c "whatever" i get:
[-] connect ui: Timer expired
and that's it. when i run bin4ry rooting i get permission denied i'm guessing on places where it needs to get into fastboot screens.
bought fastboot and now i can get fastboot only through poweron process. which is good! i've downgraded to 7.2.3
July 2017
File: Root_Master_1.3.6_Cekas.apk
VirusTotal: 31 / 61
Root if you like to be hack !
Tried the fastboot oem get_identifier_token and getting command unknown, OEM unlocking is checked in the developer options. anyone else seeing this? this is on a u11 life shipped from t-mobile..
tried Twinnfamous's suggestion using the htc fastboot from their dev site and got the same results...
C:\fastboot-win>dir
Volume in drive C has no label.
Volume Serial Number is 1211-9B14
Directory of C:\fastboot-win
11/11/2017 05:12 AM <DIR> .
11/11/2017 05:12 AM <DIR> ..
11/10/2017 01:39 PM 1,542,656 adb.exe
11/10/2017 01:39 PM 97,792 AdbWinApi.dll
11/10/2017 01:39 PM 62,976 AdbWinUsbApi.dll
11/11/2017 05:10 AM 183,651 fastboot.exe
11/11/2017 05:10 AM <DIR> __MACOSX
4 File(s) 1,887,075 bytes
3 Dir(s) 99,885,707,264 bytes free
C:\fastboot-win>fastboot devices
HT7AL1C00XXX fastboot
C:\fastboot-win>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.001s
tjablonowski said:
Tried the fastboot oem get_identifier_token and getting command unknown, OEM unlocking is checked in the developer options. anyone else seeing this? this is on a u11 life shipped from t-mobile..
tried Twinnfamous's suggestion using the htc fastboot from their dev site and got the same results...
C:\fastboot-win>dir
Volume in drive C has no label.
Volume Serial Number is 1211-9B14
Directory of C:\fastboot-win
11/11/2017 05:12 AM <DIR> .
11/11/2017 05:12 AM <DIR> ..
11/10/2017 01:39 PM 1,542,656 adb.exe
11/10/2017 01:39 PM 97,792 AdbWinApi.dll
11/10/2017 01:39 PM 62,976 AdbWinUsbApi.dll
11/11/2017 05:10 AM 183,651 fastboot.exe
11/11/2017 05:10 AM <DIR> __MACOSX
4 File(s) 1,887,075 bytes
3 Dir(s) 99,885,707,264 bytes free
C:\fastboot-win>fastboot devices
HT7AL1C00XXX fastboot
C:\fastboot-win>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Click to expand...
Click to collapse
Setting up the directory is always a ***** - I always found it easiest to open a command prompt in that folder so you don't need to type the directory first. I'm not sure what version of Windows you are running (if it's Windows at all) but here are some instructions for one version. I believe last I checked it changed but let me know if it helps. https://www.onmsft.com/news/open-command-prompt-specific-windows-10-file-directory
windows 10 fall creator edition... Appears that "adb devices", " adb reboot bootloader" and "fastboot devices" works and returns the correct information..
tjablonowski said:
Tried the fastboot oem get_identifier_token and getting command unknown, OEM unlocking is checked in the developer options. anyone else seeing this? this is on a u11 life shipped from t-mobile..
tried Twinnfamous's suggestion using the htc fastboot from their dev site and got the same results...
C:\fastboot-win>dir
Volume in drive C has no label.
Volume Serial Number is 1211-9B14
Directory of C:\fastboot-win
11/11/2017 05:12 AM <DIR> .
11/11/2017 05:12 AM <DIR> ..
11/10/2017 01:39 PM 1,542,656 adb.exe
11/10/2017 01:39 PM 97,792 AdbWinApi.dll
11/10/2017 01:39 PM 62,976 AdbWinUsbApi.dll
11/11/2017 05:10 AM 183,651 fastboot.exe
11/11/2017 05:10 AM <DIR> __MACOSX
4 File(s) 1,887,075 bytes
3 Dir(s) 99,885,707,264 bytes free
C:\fastboot-win>fastboot devices
HT7AL1C00XXX fastboot
C:\fastboot-win>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Click to expand...
Click to collapse
I just make a new folder put fastboot in the folder then hold shift and click right click then menu will show option to open command window here. Then fastboot devices then the other commands once it shows.
Another thing I do is install HTC sync then uninstall it after it installs htc driver installer. Are u trying what I'm mentioning?
have done both of those, still no joy...
tjablonowski said:
have done both of those, still no joy...
Click to expand...
Click to collapse
what mode are u in when trying? U need to be in download mode
shows the last time I touched a HTC model, the download mode worked. Always have to be different I guess...Tks
tjablonowski said:
shows the last time I touched a HTC model, the download mode worked. Always have to be different I guess...Tks
Click to expand...
Click to collapse
Yea they switched it up around the m9. Happy u got it done.
U11 life has Android One system, not HTC Android. Maybe, the treatment for this phone series is different from U11?
dieterhaack said:
U11 life has Android One system, not HTC Android. Maybe, the treatment for this phone series is different from U11?
Click to expand...
Click to collapse
There's 2 versions 1 with sense and the Android one version
Once I enter the token request, it just says waiting for device, and nothing else happens.
jdmjunkee7 said:
Once I enter the token request, it just says waiting for device, and nothing else happens.
Click to expand...
Click to collapse
Are you in download mode? What operating system are you using? Be specific to get help faster.
Yes im in download mode. Android 7.1.1. Ive checked the option in developer mode for allowing unlocking.
jdmjunkee7 said:
Yes im in download mode. Android 7.1.1. Ive checked the option in developer mode for allowing unlocking.
Click to expand...
Click to collapse
Are u on windows 10 or Linux? Do u have the drivers installed is adb debugging turned on as well?
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
jdmjunkee7 said:
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
Click to expand...
Click to collapse
Did you install fastboot/adb?
jdmjunkee7 said:
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
Click to expand...
Click to collapse
I always uninstall sync and just keep the HTC drivers installer in programs. Are you using powershell because I always use cmd
jdmjunkee7 said:
I'm running windows 10 and adb debugging is on as well. as far as I know the drivers are installed. I installed sync manager and everything.
Click to expand...
Click to collapse
Unzip the files then use cmd and cd /the folder here
Then type fastboot devices while in download mode and if it shows. fastboot with the numbers then your good to go. Or while booted u can do adb devices and it will show if your connected. I do know that on my Asus I can only get fastboot and adb to work on the 2.0 USB port it never connects on my 3.0 ports. I hope this gets u squared away. Report back your findings as it may help others that have the same issue.
So, I think I've managed to salvage my bricked Stylo, I somehow also managed to root my Fiance's LG G Stylo that's on the 6.0 update... this is a guide on how to flash a TWRP Recovery I made of a rooted LG G Stylo that is running Android 6.0 This can get you out of a brick or just give your spare phone root access.
Since I can't find any ways to fix this problem on the internet I'll post what I did here so hopefully I can get some other people out of deep water with their phone.
Stylo.zip
I'm going to assume that if you are following these instructions you have already downloaded and extracted the .zip file named Stylo onto your desktop.
All of these files are in the Stylo folder, so you should only have to download Stylo.zip
Minimal ADB & Fastboot installer
LG Phone Drivers
TWRP Backup file
recovery.img
1. Install minimal_adb_fastboot_v1.4.1_setup into the folder you extracted Stylo.zip in
(Install PhoneDrivers if you have not already)
2. Enable USB Debugging on your phone
(If you are boot looping, you should still be able to boot into the bootloader with
minimal adb fastboot just plug it in and let it do it's bootloop while you try
booting into the bootloader really quick, this may take some trial and error)
3. Launch MAF32.exe
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
5. Next you will need to type:
adb reboot bootloader
Now, the powershell screen should look like this:
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
PS C:\Users\Hyperion\Desktop\Stylo> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo>
6. Once you are in the bootloader type:
fastboot boot recovery.img
(If you opened the PowerShell window by holding shift and using the right click menu,
the recovery.img file should load on its own, your PowerShell window should now look something like this)
PS C:\Users\Hyperion\Desktop\Stylo> adb devices
List of devices attached
LGMS6318bb1ce9a device
PS C:\Users\Hyperion\Desktop\Stylo> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo> fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.367s]
booting...
OKAY [ 0.011s]
finished. total time: 0.380s
finished. total time: 0.379s
PS C:\Users\Hyperion\Desktop\Stylo>
7. Once TWRP boots up on your device you will need to navigate to Backup
Uncheck everything but boot
Start the backup process
(We are making a backup of boot
so we can take the name of the folder
it makes in /sdcard/TWRP/BACKUPS
and copy/paste that to the rooted backup file.
TWRP will create a backup of your
boot animation that contains your PHONE ID #
In my case it created a file named LGMS6318bb1ce9a )
8. Open your sdcard contents on your computer
navigate to /sdcard/TWRP/BACKUPS
Copy the name of the new folder that was created (Mine is LGMS6318bb1ce9a)
Open the Stylo folder on your Desktop \Desktop\Stylo\TWRP\BACKUPS
Paste the new folder name over the folder titled (Paste Here)
Overwrite the folder in /sdcard/TWRP/BACKUPS that contains
the boot animation with the new folder from \Desktop\Stylo\TWRP\BACKUPS
9. If you are not in TWRP on your phone any more, repeat steps 3. - 6.
10. Once in TWRP click WIPE in the top right, and Swype to Factory Reset
(Unless your backup file is being loaded from Internal Storage)
11. Navigate to RESTORE in TWRP, find your Backup file in the /TWRP/BACKUPS directory
LEAVE EVERYTHING CHECKED!
(If you uncheck anything the phone will not be rooted upon restore of the backup)
(Alternatively you can uncheck Data and have a fresh install of 6.0 with no root.)
The rooted backup should be installing 4144mb worth of data.
I left a few apps on the desktop that I figured would help some people out
Hope this worked for you, getting root on these phones is a *****.
-Mike
Screenshots were taken after the first boot of the Recovered device
Hardware Info
Software Info
Root Check
Can't make it past adb reboot bootloader, phone goes into a unlock mode and freezes up
I know a site that has the QFIL files necessary to actually unbrick a hard bricked Stylo H631. I'm not sure if I'm allowed to link them ..but I will tell you they charge 11.99USD. I'm hoping to have the $ to do it Friday...if I can...I'll give it a try and post findings here
Sent from my ROOTED LG-TP260 Thanks to Messi yet again!!!
SoonersChuck said:
I know a site that has the QFIL files necessary to actually unbrick a hard bricked Stylo H631. I'm not sure if I'm allowed to link them ..but I will tell you they charge 11.99USD. I'm hoping to have the $ to do it Friday...if I can...I'll give it a try and post findings here
Sent from my ROOTED LG-TP260 Thanks to Messi yet again!!!
Click to expand...
Click to collapse
I'm still waiting from someone in the comments from that site to confirm it's not a scam.
I need to find out the pin test spots on the h631/ms631... anyone know of a diagram or schematic floating around??? If so, I may have this figured out...don't want to poke around on my only board and make it completely useless
SoonersChuck said:
I need to find out the pin test spots on the h631/ms631... anyone know of a diagram or schematic floating around??? If so, I may have this figured out...don't want to poke around on my only board and make it completely useless
Click to expand...
Click to collapse
You mean a diagram of the emmc?
Anything that shows me where to touch to get the desired reaction
---------- Post added at 08:50 PM ---------- Previous post was at 08:49 PM ----------
Clk Dat0 gnd...those spots
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
trejose said:
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
Click to expand...
Click to collapse
ya gotta check all the boxes possible after going into the MOUNT options when in TWRP. always before doing almost anything in TWRP. sometimes its persistant, sometimes not depending on device.
---------- Post added at 08:15 AM ---------- Previous post was at 08:09 AM ----------
trejose said:
When i type "fastboot boot recovery.img" in command prompt it comes up with a message saying "cannot load 'recovery.img': No such file or directory". Can someone help? The recovery file is on my desktop
---------- Post added at 11:56 PM ---------- Previous post was at 11:07 PM ----------
fixed my earlier issue but now when my device loads TWRP and i select to back up "boot", it fails.
---------- Post added 19th March 2018 at 12:44 AM ---------- Previous post was 18th March 2018 at 11:56 PM ----------
how do i open the sdcard contents on my computer?
Click to expand...
Click to collapse
Enable MTP in the MOUNT options while in TWRP
I can't seem to get my T-Mobile Stylo 5 to go into fastboot mode. Adb reboot bootloader just reboots the phone for me. Maybe a downgrade is required?? Also I just used platform-tools adb and fastboot. Build# PKQ1.190302.001
using peter's twrp.
what are the steps?
Follow the steps from this link to switch to stock ROM.
I followed fastboot method in Linux pc it works.
---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------
Steps I followed.
In Linux (ubuntu):
Install adb and fastboot using the following command
sudo apt install android-tools-adb android-tools-fastboot
Download the fastboot ROM from here
Extract the downloaded ROM tar ball.
Boot the phone into fastboot mode by pressing volume-down + power.
Connect the phone to PC through USB cable.
In the terminal go to the extracted ROM directory and execute "./flash_all.sh" as sudo
sudo su
./flash_all.sh
You will get text messages of flashing in the terminal and finally the device will reboot into stock ROM.
First boot will take some time.
Hope this helps