Database Develop

Going Crazy/Brick

Here is the story in a nutshell I flashed xdabbeb's bootstack, then his rom. Then I did something stupid such as wipe everything folks, I mean everything. So my phone then restarted and I am able to get into recovery twrp 2.7.
I have tried in twrp to sideload, mount neither which work.
I have my drivers installed it says in device manager when I plug the phone up for download mode
android- galaxy nexus adb
and under ports it says LGE AndroidNet for VZW ADB Interface com41
I tried lg flash tool, tried with old vs98010b rom
pid:
imei:
model:
dll: vs980
bin: vs98010b_13.tot
swv:
swov:
model information check fail!
00000000
I really need help guys, are there any adb commands I can type or are there any drivers I need to install

Ok when i hold the up and plug in it takes me to fastboot
[500] fastboot mode started
[550] udc_start()
[720] reset
[730] portcharge
[740] reset
[750] portcharge
and the device only registers as android under other on my computer
i've installed lg drivers

How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot

timenewton said:
How can you fastboot flash? When I hold up and plug in for fastboot my computer wont register a driver just shows android what are the commands and how do I use fastboot
Click to expand...
Click to collapse
Download mode is not going to work because the laf partition (this allows for download mode to work) is wiped when you flash xdabbeb's bootstack in favor of fastboot mode.
I suggest you pm xdabbeb; he will guide you on the steps to using the necessary fastboot commands to get your phone working again. He's already helped a few people that were in the same situation as you are in right now.
Fastboot is good because you can write certain partitons at a time without having to .tot and wipe your whole phone.
You could also flash his xdabbeb_vs98024a_laf.zip http://www.androidfilehost.com/?fid=23329332407586639 file in TWRP 2.7 to restore download mode, but you will end up wiping your whole phone by using the LG Flash Tool, even your sd card when you restore your phone.
You said you "wiped everything", I'm not sure if that means your sd card too, if so, then that might be the easiest thing to do since you still have access to recovery. You will need an otg cable and a flash drive to mount the flash drive in TWRP 2.7 and flash the file, unless you can side load the file with adb.
Either way, like I mentioned earlier, it might be a good idea to pm xdabbeb first.

Hey my phone is already wiped even sdcard, but the thing is i cant flash that file because I can not get it on my phone. So ill ask xdabbeb the fastboot commands. Yeah and I read about the otg cable, ordered one of those babies should be here this saturday and hopefully it will mount my flash drive in that case id be golden untill then ill see what mr xdabbeb has to say.
cant sideload
everytime i try to sideload the file it just says cant read file or something like that
And I really appreciate you responding. Always nice to get support from somebody when your just sitting here and your phone seems like it hasnt been working for an eternity. Almost depressing not hearing from anyhbody and just seeing all the views but no replys. Thank you

Hey there...Fastboot is about as basic/simple/reliable as it comes. If you have adb/fastboot set up properly then command is:
fastboot flash <partition> <filename>
for example:
fastboot flash recovery recovery.img
In your case, you claim to have a working recovery (twrp 2.7), but are unable to copy files from your computer to your phone. It sounds like you don't have the proper drivers installed so that you can use adb from recovery. This is a common/known issue with windows and I believe I replied to you in the rom thread already about this, but you need to install/use Koush's universal adb driver and simply copy the rom file over to your phone using the following command:
adb push <filename> /sdcard/
After you have the file there you can flash it as normal in recovery.
If you want to use a kdz/tot method to restore your phone, just download the laf zip file from my thread, extract the laf.img file from the zip, and use the following command to put it in place:
fastboot flash laf laf.img
Then you can go about the tot restore method described in the thread here. You don't need to put the tot file itself on your phone. It just needs to be on your computer.

I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>

timenewton said:
I get to sdk and open cmd
type adb devices it says
List of devices attached
0215817d960ce580 sideload
Then I type adb push rom.zip /sdcard/
error: closed
When phone is plugged in for adb device manager says under android device- Google galaxy Nexus ADB Interface
I have universal drivers installed and I goto device manger to update drivers where clockworkmod is installed and it doesnt do anything
Fastboot it says in other devices in device manager
Android
PCI Data Acquisition and Signal Processing Controller
I type fastboot flash recovery laf.img
<waiting for device>
Click to expand...
Click to collapse
Wait, I'm confused here a little bit. Are you trying to do sideload mode in TWRP or are you using fastboot mode?
And the command you typed is not correct fastboot flash recovery laf.img...you don't want to do that...this would flash the laf.img in your recovery partition.
xdabbeb referenced two methods to you...one was pushing a Rom to your sdcard and then flashing that Rom in TWRP to get your phone booting...the other was to flash the laf.img file and do a .tot if that's what you prefer.
It seems like you want to do a .tot restore, so do the second method xdabbeb suggested.
Get into fastboot mode and type fastboot flash laf laf.img
Make sure you use the correct laf.img...you can extract it from the zip in my previous post/link.
After this your download mode should be working again.

I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?

Even when i try to flash the laf it keeps saying waiting for device. I have the drivers koushu installed and lg

timenewton said:
I was trying either one
For fastboot I downloaded xdabbebs laf
the image file in his file is laf.img, if thats not the right file then where is the recovery.img
So the recovery.img would have been one that i made?
and laf is so I can us lg tool to tot flash?
Click to expand...
Click to collapse
Yes, download xdabbeb's laf.img, it's the link I gave you originally. You will have to take out the laf.img file from the zip file that is called xdabbeb_vs98024a_laf.zip
The recovery command he gave was just an example, there was no need for you to use it.
Yes, flashing the laf.img will fix your download mode and you will be able to do the .tot method.

What am I suppose to do about it saying wiating for device, its not detecting it

timenewton said:
What am I suppose to do about it saying wiating for device, its not detecting it
Click to expand...
Click to collapse
That sounds like a driver issue. Reboot your computer and turn off the phone and start again. See if that helps. You can also remove the drivers and re-install...I suggest you reboot your computer every time you install new drivers.
EDIT:
Are you using a newer adb.exe from your android sdk? If you have ioroot25 installed on your computer I suggest you use the folder/files from there. It has a newer adb.exe in there; put your laf.img file in that folder too if you do use that instead, and run the command prompt from within that folder.

Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.

Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible

timenewton said:
Ok when my phone is plugged into my comp, im on win 7 it shows up as android under other devices when started in fastboot mode. When I browse to the driver location to load for the android it says no driver found for it.
Click to expand...
Click to collapse
timenewton said:
Yes i just installed the sdk like 2 days ago so I know its current.
As far as the driver situation, why would I need to uninstall if it isnt even installing a driver.
This is terrible
Click to expand...
Click to collapse
For me it shows up under "ADB Interface", but I don't have the universal driver installed.
I didn't realize it wasn't installing the driver for you.
You have to get that driver going or you won't be able to get your phone fixed. Maybe try a different usb port or a different computer.

Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?

timenewton said:
Man yeah mine doesnt look at all like that. Im uninstalling lg driver and universal one and clearing temp folder. Then restart and reinstall maybe that will work. So its just the koushu driver that works for fastboot and adb right?
Click to expand...
Click to collapse
Yeah, it should work. I've read posts by others stating that it works.

Yep just reinstalled the universal drivers, plug phone up into fastboot and still get the same result

Can you perhaps send me that driver you have? Because I know if you have that one and it works for you it SHOULD work for me. Murphs law is killing me. I can pm you my email address

[Root] Root and TWRP for R

Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years

Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.

One more just in case.

Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?

hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.

I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!

hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.

Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.

Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?

adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app

reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.

adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.

tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!

HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!

I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...

zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app

Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there

zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.

Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)

zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.

[Q] Erased Userdata how to push rom to phone

Was running CM12 nightlies that auto encrypted, so went to format data to remove encryption but keyboard in twrp wasnt accepting any characters so hence i wasnt able to decrypt, so i bootloader->fastboot erase userdata...now im back in twrp phone still encrypted (i know the password so im ok) but now theres obviously no rom on the phone how do i push a rom & kernel to my phone adb sideload seems to be hanging on "starting adb sideload feature" and when im in bootloader mode adb doesnt find my device

Fastboot erase userdata doesn't remove the ROM.
Adb isn't designed to work in bootloader. Use of in recovery. You can use adb to push files to /sdcard
See my thread here if you need help
http://forum.xda-developers.com/showthread.php?t=3006500

Plug the phone in to your computer and go to mount and enable mtp. Then go to your computer and copy and paste the rom zip as well as other zips (gapps kernel etc) onto your phone.
Sent from my Nexus 6 using Tapatalk

mak213 said:
Was running CM12 nightlies that auto encrypted, so went to format data to remove encryption but keyboard in twrp wasnt accepting any characters so hence i wasnt able to decrypt, so i bootloader->fastboot erase userdata...now im back in twrp phone still encrypted (i know the password so im ok) but now theres obviously no rom on the phone how do i push a rom & kernel to my phone adb sideload seems to be hanging on "starting adb sideload feature" and when im in bootloader mode adb doesnt find my device
Click to expand...
Click to collapse
Kinda had that issue I just used OTG with the ROM on it that solved my problem

or you can adb push files to your phone, via adb while you are in your recovery. but from what i understand/have heard, cm kernel does not allow decryption.

rootSU said:
Fastboot erase userdata doesn't remove the ROM.
Adb isn't designed to work in bootloader. Use of in recovery. You can use adb to push files to /sdcard
See my thread here if you need help
http://forum.xda-developers.com/showthread.php?t=3006500
Click to expand...
Click to collapse
ya but before i fastboot erase data, i did do a advanced wipe in recovery and did remove rom so cant boot ..
zephiK said:
Plug the phone in to your computer and go to mount and enable mtp. Then go to your computer and copy and paste the rom zip as well as other zips (gapps kernel etc) onto your phone.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
also when i try to mount i get no valid storage partitions found for mtp

simms22 said:
or you can adb push files to your phone, via adb while you are in your recovery. but from what i understand/have heard, cm kernel does not allow decryption.
Click to expand...
Click to collapse
adb is not being read for some reason in recovery, adb sideload is failing to start (never worked for me )

simms22 said:
or you can adb push files to your phone, via adb while you are in your recovery. but from what i understand/have heard, cm kernel does not allow decryption.
Click to expand...
Click to collapse
no they just don't give you an option to not encrypt with they're kernel, so you must flash another kernel after every nightly etc.

mak213 said:
no they just don't give you an option to not encrypt with they're kernel, so you must flash another kernel after every nightly etc.
Click to expand...
Click to collapse
right, that's the direction i was going..
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
mak213 said:
adb is not being read for some reason in recovery, adb sideload is failing to start (never worked for me )
Click to expand...
Click to collapse
is the driver installed? and im not a adb sideload person, but adb push works great for me. just open the main page of twrp, dont press any options, then try adb push.

simms22 said:
is the driver installed? and im not a adb sideload person, but adb push works great for me. just open the main page of twrp, dont press any options, then try adb push.
Click to expand...
Click to collapse
Yea drivers installed was using adb few hours before incident, i unfortauntely resorted nexus toolkit and flashing stock to see if that works for some reason after i fastboot reboot'd out of fastboot it doesnt open twrp anymore just bootloops twrp, let ya know how it goes
EDIT: Just ended up flashing stock image and restarting from step 1 :/

mak213 said:
Yea drivers installed was using adb few hours before incident, i unfortauntely resorted nexus toolkit and flashing stock to see if that works for some reason after i fastboot reboot'd out of fastboot it doesnt open twrp anymore just bootloops twrp, let ya know how it goes
Click to expand...
Click to collapse
can always fastboot twrp again, or fastboot boot it

mak213 said:
adb is not being read for some reason in recovery, adb sideload is failing to start (never worked for me )
Click to expand...
Click to collapse
What does adb devices say when booted in recovery?

Adb Sideload

Hello all,
I made a big mistake and wiped my Sd card on my rooted, Unlocked M7. I was able to get recovery(TWRP) back on but for the life of me cannot sideload a Rom on it? At the moment it has no OS. So that means I cannot open usb debugging so I could manually place the ViperOne rom back on the SD. I've never sideloaded anything but after watching many youtube videos and failing ( cannot read ROM.zip) its driving me nuts. Is there maybe an easier way? Maybe something else I can try?
I have tried to load for both desktop and platform tools( both I can see my device).

Splitshot said:
( cannot read ROM.zip)
Click to expand...
Click to collapse
This error is usually caused by the file being in the wrong location. Make sure "ROM.zip" is in the same folder where you have adb and fastboot on your computer.
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
TWRP 2.6.4.0 also include mtp drivers so you can see your device storage on your ocmputer when booted in recovery mode.

Splitshot said:
Hello all,
I made a big mistake and wiped my Sd card on my rooted, Unlocked M7. I was able to get recovery(TWRP) back on but for the life of me cannot sideload a Rom on it? At the moment it has no OS. So that means I cannot open usb debugging so I could manually place the ViperOne rom back on the SD. I've never sideloaded anything but after watching many youtube videos and failing ( cannot read ROM.zip) its driving me nuts. Is there maybe an easier way? Maybe something else I can try?
I have tried to load for both desktop and platform tools( both I can see my device).
Click to expand...
Click to collapse
alray said:
This error is usually caused by the file being in the wrong location. Make sure "ROM.zip" is in the same folder where you have adb and fastboot on your computer.
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
TWRP 2.6.4.0 also include mtp drivers so you can see your device storage on your ocmputer when booted in recovery mode.
Click to expand...
Click to collapse
Like alray said flash TWRP 2.8.4.0 and the phone will be seen in windows and you can just copy the file to the phone and flash it

I already had a "Install recovery v1.2" in my downloads so I tried this because I was unsuccessful with all the other attempts and low and behold it worked. although its an older version of TWRP (2.6.3). would it make a difference not having the latest? now that recovery is there I was hoping to push a ROM then update the recovery through root manager.
I just read alray's last line about the mtp drivers. OK, I will first get my folders working better, upgrade to a newer version TWRP and then push a rom. Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.

Splitshot said:
I already had a "Install recovery v1.2" in my downloads so I tried this because I was unsuccessful with all the other attempts and low and behold it worked. although its an older version of TWRP (2.6.3). would it make a difference not having the latest? now that recovery is there I was hoping to push a ROM then update the recovery through root manager.
I just read alray's last line about the mtp drivers. OK, I will first get my folders working better, upgrade to a newer version TWRP and then push a rom. Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Click to expand...
Click to collapse
you don't need adb at all if you load TWRP 2.8.4.0 you just copy the file in windows like to a flash drive

Splitshot said:
upgrade to a newer version TWRP and then push a rom.
Click to expand...
Click to collapse
If you are going to update twrp to 2.8.4.0, you will not need to push or sideload the rom, just copy it to your phone storage using the windows explorer. Navigate to "my computer --> One --> Internal storage" and copy your rom there.
Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Click to expand...
Click to collapse
These 2 commands means nothing. :laugh: SO no, there is no difference between these 2 commands, both will fail lol
if you want to use adb push:
Code:
adb push name_of_rom.zip /sdcard
if you want to sideload:
Code:
adb sideload name_of_rom.zip
But like i said, you don't need to use these commands to get your rom on your phone if you are gonna update twrp to 2.8.4.0.
download twrp 2.8.4.0, save it to the same folder where you have adb and fastboot installed on your computer. Open a command prompt from that folder, boot your phone in bootloader/fastboot usb mode.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery mode
you'll now see your phone storage on your computer, copy (drag and drop) your rom.zip to your phone storage.

About MIUI EU ROM Brick and won't be able to connect to PC or OTG (Lose usb port)

Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)

This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...

zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
zopostyle said:
This rom (muiu 13) can only be installed via fastboot method. You can't use twrp or update method...
Click to expand...
Click to collapse
I was talking about the Miui 12.5 update but it's good to know it

ZeroNoTime said:
Well, all of this started when i tried to install the MIUI EU rom by TWRP, the surprise will come when the phone didn't boot. I've tried this on January of this year.
I tried everything, change port, motherboard flex, usb cable, another PC but no works.
Today i found a folder on /dev/usb-ffs/fastboot and it's empty but the adb folder (/dev/usb-ffs/adb) contains three files (ep0, ep1 and ep2). I'm not a programmer but maybe that fastboot folder would have that files.
Reading the default.prop i found the "Redmi K30s Ultra" name on ro.product.model
All of this make me think on the posibility of my phone will never be recovered, the phone only boot on fastboot and twrp but don´t detect the PC maybe for the files which is needed to boot or recognized is lost.
The TWRP version is ( 3.5.2_10 by Master and the phone gets the E:Unable to decrypt data error)
Click to expand...
Click to collapse
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip

4. Have you tried simply formatting data from TWRP before attempting to boot?

Dobsgw said:
I don't think there are any issues with the hardware
1. Are you sure that you have installed the correct drivers for the device in windows?
2. Have you tried using a different PC? Alternatively try to use Linux
3. Have you tried adb sideload method from TWRP? eg) adb sideload rom.zip
Click to expand...
Click to collapse
Yep, i tried everything but doesn't work
I only have access to twrp and fastboot but the usb connection doesn't work

Dobsgw said:
4. Have you tried simply formatting data from TWRP before attempting to boot?
Click to expand...
Click to collapse
Yep but shows the message e: Unable to decrypt FBE device