Hey xda members,
My name is Pierre, from France and new owner of X820 version 6GB 64GB (from Aliexpress).
I made a big mistake yesterday, wiping from TWRP all data (Sytem, applications etc.)
Now if I put "ON" again, it is just showing "EUI" logo, without end
I have still access to TWRP but no backup, not .img loaded in the phone.
I can't connect and load from USB the ROM, so I am honestly lost.
If you have just any idea,how to solve it! Please let me know
Thank you very much, and good evening,
TWRP has a backup solution for you. I did this same misstake like you.
In Advanced settings you can run ADB SIDELOAD.
I hope you have proper ADB drivers in your PC and command prompt in Windows is your friend.
With ADB SIDELOAD you can install ROM from your PC via USB to your bricked phone. ADB uses whole base of commands to control what you can do.
Follow this steps:
https://forum.xda-developers.com/showthread.php?t=2318497
Twrp also supports MTP so you should also be able to copy a rom on the sdcard when in twrp.
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Thank you Razor, mikey and cr3pt !
If I am not mistaken, you provide me: 2 different solutions (ADB Sileload or abd push ROM).
It does mean, if I select the "one more easy" :
1. I boot in TWRP my phone
2. connect by USB (ADB drivers must be installed). Usually it is written MTP or "Android" but I can't see the external drive in Win10.
3 Then adb push rom_file.zip /sdcard in the Wincommand
4. wait and after disconnect USB
Then I will find the ROM to install in my phone.
Is it correct?
Yes
If you have TWRP, connect the phone to your computer, mount storage in TWRP, copy the rom of your choice, and install it. That simple
Sent from my Le X821 using Tapatalk
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
kanagawaben said:
I use TWRP and always just drag and drop the ROM zip from PC to the phone's internal storage and it shows up in TWRP under install. It's super easy. As long as you have the correct drivers installed on your PC you shouldn't need to use adb.
Click to expand...
Click to collapse
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
install ADB, all necessary drivers. without that you can only dream about correct fix'a
piyerre said:
Hey
My computer (Win 10) does NOT recognized sometimes: MTP, or sometime "Android". So in fact, I never the external storage in my windows.
That is why I can not simply "drop" unfortunately.
Should I maybe install ADB again?
Click to expand...
Click to collapse
I'd try to start again clean. First completely remove adb and android device drivers from your computer. Then boot your phone into TWRP and connect it by usb to your computer and see if it auto installs the right drivers. If not, I guess you have to find where to download them from to install manually.
cr3pt said:
install ADB, all necessary drivers. without that you can only dream about correct fix'a
Click to expand...
Click to collapse
Can you give me please a link with the correct ADB and the correct drivers.?
I can't see the external drive even if adb devices gives me OK result.
Thank you,
you don't need external drive - correct is adb device. just push file when is visible in device manager
Hello !
It does work perfect, I finally use the "adb push" function!
Thank you very much all
cr3pt said:
just use:
fastboot boot twrp.img (if TWRP you have in twrp.img file)
mobile boot in TWRP
then
adb push rom_file.zip /sdcard
after OK just install that rom from SDCARD via TWRP...
Click to expand...
Click to collapse
It works! Thank you very very much!
Bro Its is new security added in windows 10... U can only install official and signed drivers in windows 10.. U should turn it off.. only then u can access adb and fastboot...
One more thing bro...
If u have lost every thing, but u r able to boot in twrp, then follow me:
1. Download any rom for le max 2 U want to
2. After downloading,copy it in ur pendrive
3.Boot in twrp
4.connect the pendrive to ur device using OTG adapter
5.Mount USB storage
6.wipe every thing again.
7.After installation,reboot
8.first boot may take time and then wgwghrussuwgskaaiiawg (U know the rest??)
Related
Ok so I was trying to install a custom recovery on my P500 and when it turned on it gave me this message
fast boot mode started
udc_start
Click to expand...
Click to collapse
I plug it in it gives me
fast boot mode started
--suspend--
--reset--
--port/change--
--reset--
--port/change--
Click to expand...
Click to collapse
I tried out this method: http://forum.xda-developers.com/showthread.php?t=1088046
After keying the fastboot commands in it says <waiting for device>. Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
I'm still on my stock ROM (untouched), phone is rooted (duh) and this is my first attempt to install a custom recovery.
Not allowed to post on that thread ofc, my first post here. All help greatly appreciated. Thanks
Here is the Simple way ..try it
this link for latest working Rom >>
http://forum.xda-developers.com/showthread.php?t=946354
how to root >>
Enable USB debugging on your phone by going to Settings –> Applications –> Development. Check the ‘USB Debugging’ option.
Make sure you have a SD card inserted and mounted in your phone (Don’t know if it’s necessary but before proceeding further I formatted my SD card after taking a backup of the data in it. Why take a risk? Smile)
Download the GingerBreak APK from XDA Developers and get it onto your phone.
Install it by browsing to the GingerBreak APK in any file manager.
Open GingerBreak from your app drawer and press the root button.
Wait for a few minutes. If there are no problems, the device will reboot itself. (The reboot will take quite some time.)
You will see a SuperUser app in your app drawer after the reboot. Open it and see if it is working.
You now have a rooted Optimus One P500 phone.
Now install custom recovery
Follow the below steps to install custom recovery on your LG Optimus One P500.
Install Android Terminal Emulator from Android Market.
Download the file "amon_ra_recovery_installer.zip" from here or here.
Check the MD5 hash value of the downloaded ‘zip’ file. You can use HashTab to do this. Right click on the downloaded file and ensure the MD5 matches 86db8a52b01f049cadb8f097a4c5bd9e.
Extract the contents of the ‘zip’ file to the root of the SD card (Don’t extract inside any folder. For example if your SD Card is mounted on J: in Microsoft Windows then the four extracted files should be right under J:/ like J:/flash_image)
Open the terminal emulator app on your phone and type ‘su’ without the quotes. This will prompt a popup on your phone from the SuperUser app asking you whether you want to give root permissions for the terminal emulator app. Click ‘Allow’ and proceed. The shell prompt will change from the previous user shell ‘$’ to root shell ‘#’ in the emulator.
Now type in the following command and press Enter. The custom recovery will be flashed on to your phone and it will reboot into Custom Recovery.
sh /sdcard/rf.sh
Shut down your phone and boot into Recovery using the Volume Down, Home and Power switch keys. You can move through the options using the volume up/down keys. Use the Menu button to select the option.
In the recovery menu, select Backup/Restore, then select Nand backup. What this will do is backup your current ROM on your SD card, if something goes wrong while flashing the new ROM you can simply boot into recovery and restore your previous ROM.
Connect the phone to your computer and inside Recovery main menu click the option ‘USB-MS toggle’ and then ‘USB-MS Toggle SDCard’. This will unmount the SD card so that you can see it in your computer. Backup everything from your SD Card. Eject from computer and toggle USB again from recovery to mount the SD card back in phone.
Though it is not a necessity for this ROM, I would suggest partitioning your SD card to create swap and ext partitions. The ext partition will come in use if you want to install apps onto your SD card later. This is different from what you see in Froyo versions of Move to SD option. Partitioning will format your SD card, so make sure you backup your SD card as mentioned in Step 3.
Go back to the recovery menu again and select ‘Partition sdcard’. Then select ‘Partition SD’. Create a swap partition of size 0 and ext partition of size 512. Once done hit Back to go again to the ‘Partition sdcard’ menu. Convert the partition you just created to ext 3 and then ext4 using the options ‘SD:ext2 to ext3’ and ‘SD:ext3 to ext4’.
Toggle USB from recovery again. Inside the SDcard create a folder AAA and copy the ROM you downloaded in Step 1 into the folder ‘AAA’ on your SDCard. Once done, eject the SD card and toggle USB again to mount the SD Card in the phone again.
Go to the Wipe option in the recovery menu and wipe userdata, /data, /sd-ext, /sdcard/.android_secure, /cache, ‘Dalvik-cache’
Then go to the Flash Zip option in the recovery menu and select the zip file you copied in Step 6.
Sit back and relax while the zip is flashed. Once recovery shows that flashing is complete, reboot phone from recovery. The first boot will take quite some time.
Enjoy Gingerbread 2.3 on your LG Optimus One P500.
@ above completely unrelated to his problem.
Sent from my LG Optimus One P500 using XDA App
Appreciate your post but it has nothing to do with query sadly.
I was doing what you've mentioned in the installing recovery section when things went wrong.
I run Win7 x64 btw.
istoner said:
Some Google hits told me that it's because I don't have latest USB drivers. I'm sure I do, but I've re-installed them just to be sure. But to no avail.
Click to expand...
Click to collapse
That is correct - drivers issue.
1/ Add DEVMGR_SHOW_NONPRESENT_DEVICES to your environment on Windows and set the value to 1. (In Advanced system settings, Google if you do not know how.) Log off and log back on.
2/ Run devmgmt.msc
3/ There, View - Show hidden devices
4/ Go thru it and uninstall everything Android-related (for starters, ADB Interface and stuff under it, Disk drives, Modems, Ports (COM and LPT), USB controllers - might not be complete list above)
5/ Reboot the PC.
6/ Install the latest drivers for your phone.
7/ If it worked, once you have plugged in the phone stuck in fastboot mode, in device manager you should see Fastboot interface (Google USB ID) in ADB Interface section.
Thanks, trying that out now.
doktornator,
Thanks a bunch. It was an issue with the drivers, I tried your method a few times with little success. Then I let Windows find the drivers (out of all the things), and that worked. Relieved and slightly embarrassed that Windows could what I couldn't
Good that it works now. Fingers crossed to unbrick your phone soon.
Oh it's unbricked and ready to go again lol.
Hi, I am on Windows XP with the exact same problem.
Have tried the B2CApp for driver updates with no luck. Tried windows automatic driver installation,again no luck.
Anything else that I could try on a Win XP machine?
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
droidao said:
hi guys
Same issue here...and I've had all of the above problems (missing dll, the "waiting for device" due to the absence of proper drivers, etc) . I was able to solve everything up to step 2 of the procedure, i.e., when I type "fastboot flash recovery recovery.img" I get the error message: "cannot load recovery.img".
I tried with both the .img files extracted from the CWM link and AmonRA (thinderg). Any ideas? What am I doing wrong? This is going for hours now and I'm getting desperate!
Click to expand...
Click to collapse
is the name of the .img file recovery.img?
the command is really fastboot flash recovery (name of file).img
Yes it is...Actually I tried both ways (renaming and keeping the original name)! But I've finally figured it out!!! Here was the problem: when I installed android sdk I added the paths of the required directories (tools and platform-tools) to the system variable section so I could launch tools without writing the path all the time...However, because desperate times call for desperate (and often silly) measures, I decided to type the command cd "name-of-directory" anyway and that...made the trick.
This community is indeed great...I'm going to distribute some "thankyous" now!
I had the same problem with Win7, Updating the drivers from the device manager of w7 worked for me. Hope it helps.
Ps: will take around 15 mins updating.
my phone wont go past HTC starting screen.
How can i flash stock att rom ?
I am stuck. suggestions appreciated.
Why won't it? What did you do to get to this state? What did you flash?
The more details you give...the more likely someone will be able to help you!
well i have unlocked bootloader.
i flashed one mod for extended power menu and after that my phone wont go past HTC one screen so i wiped and did factory reset still phone wont boot.
I went in to recovery menu and formated system and now i dont know how to flash stock rom.
varuun said:
well i have unlocked bootloader.
i flashed one mod for extended power menu and after that my phone wont go past HTC one screen so i wiped and did factory reset still phone wont boot.
I went in to recovery menu and formated system and now i dont know how to flash stock rom.
Click to expand...
Click to collapse
Here is all you need to know.
HTC One FAQ
I take it you did not make a NAND backup?? Always advised to make a BU before flashing anything!
What recovery did you install?
shawman said:
Here is all you need to know.
HTC One FAQ
Click to expand...
Click to collapse
Somehow i can not access USB storage so in this case how can i put rom into internal storage?
varuun said:
Somehow i can not access USB storage so in this case how can i put rom into internal storage?
Click to expand...
Click to collapse
ADB Sideload it. Here's the stock Deodexed ROM I used when I had that problem.
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
wmg316 said:
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Click to expand...
Click to collapse
..... Is that..... Mike G.??? You're an Android Guy too!
That's me! Who is this?
wmg316 said:
That's me! Who is this?
Click to expand...
Click to collapse
Josh S. from Landmark
Small world!!
wmg316 said:
Small world!!
Click to expand...
Click to collapse
No kidding.
P.S TrickDroid is a pretty sweet ROM.
Hi
I am doing as you said but i am getting attached screen. its not working for me.
wmg316 said:
Download a ROM that you want to flash. Use ADB Sideload method.
Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher.
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload /path/to/rom.zip (e.g., adb sideload C:/ADB/[name of ROM].zip...or open the command prompt when in your adb folder; in Windows 7, go to your adb folder on your pc...use shift and right-click, open command window here...then just type
adb sideload [name of ROM].zip)
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Click to expand...
Click to collapse
Do you have TWRP recovery?
If so, did you boot device to recovery?
If so, did you then select Advanced, ADB Sideload...then swipe to start?
THEN...run the command adb sideload One_1.29.401.13_deodexed.zip
EDIT:
ADB Sideload does not work until you are in recovery, and select and run adb sideload within recovery.
Also, if you get device not recognized...run:
adb kill-server
adb start-server
then try adb sideload again...
i have clockworkmod recovery v6.0.3.1
I booted into recovery then selected install zip from sideload. but its not working as it suppose to. Am i doing something wrong?
varuun said:
i have clockworkmod recovery v6.0.3.1
I booted into recovery then selected install zip from sideload. but its not working as it suppose to. Am i doing something wrong?
Click to expand...
Click to collapse
"Fastboot erase cache"
when i checked log in to recovery its says that"failed to open adb driver control:no such file or directory"
and when i type adb devices it says
"
C:\fastboot>adb devices
List of devices attached
HT348W900356 host
"
Any clue?
I don't use CWM, so don't know anything about it. Try buying a USB-OTG cable, get a USB stick (USB flash drive) and put the ROM on the USB stick, connect USB stick to phone and mount USB-OTG in recovery. Flash from that. That's the only other thing I can think of.
Sent from my HTC One using Tapatalk 2
varuun said:
when i checked log in to recovery its says that"failed to open adb driver control:no such file or directory"
and when i type adb devices it says
"
C:\fastboot>adb devices
List of devices attached
HT348W900356 host
"
Any clue?
Click to expand...
Click to collapse
Do you have HTC Sync Manager installed? Do you have all the HTC Drivers?
UPDATE!
Finally got it working. All in one tool kit + adb sideload the rom = win
Hope this helps anyone else in the future that does this!
So I formatted data and have no ROM to flash anymore - I'm trying to mount USB but it keeps saying "E: Unable to oust 'usb-otg' - How can I get this thing to mount so I can flash my ROM back on and use the phone again!
TWRP Recovery is what I'm using if that helps
Edit: Update!
I also ran into a similar predicament a few days ago. I found adb push to be much easier than sideload. Make sure that your drivers and adb is installed on your PC (I assume Windows). In recovery mode, plug phone into USB and your PC should detect the phone but you won't be able to see phone contents; mine made a connection sound.
Then open a command prompt and type: adb push ROM.zip /data/media/ROM.zip
Rom.zip is the rom file that you want to flash, which should be in the same folder as adb. For the path, I used "/data/media" because the custom recovery defaults to that but you may be able to use "/sdcard" as well.
Then flash the rom using recovery
Click to expand...
Click to collapse
Tried to do this as well, moved AR 10.3 rom to adb folder, did the push command and it couldn't find/connect to device.
Would finding a non-aroma rom and flashing it using fastboot work?
Hello,
I rooted my Hisense Sountab MA-327 and changed some issues in the builds.prop (before I backup-ed this file first). There was no result for what I was doing after a successful restart, so I copied the backup file back to the system folder. After I restart the device, the system hangs in the boot. I tried to login with ADB to see whats went wrong, but I can can not find a good USB driver for this device. Can some please help me? The device is no useless.
- Is there a good USB driver for the Hisense SoundTab MA-327?
- What do I need the get in the system (ADB tools)?
- Or ... is there a flash/firmware for the Hisense Soundtab MA-327 somewhere available?
I really hope some can help me out.
Thanks in advance
Hans
kameraad759 said:
Hello,
I rooted my Hisense Sountab MA-327 and changed some issues in the builds.prop (before I backup-ed this file first). There was no result for what I was doing after a successful restart, so I copied the backup file back to the system folder. After I restart the device, the system hangs in the boot. I tried to login with ADB to see whats went wrong, but I can can not find a good USB driver for this device. Can some please help me? The device is no useless.
- Is there a good USB driver for the Hisense SoundTab MA-327?
- What do I need the get in the system (ADB tools)?
- Or ... is there a flash/firmware for the Hisense Soundtab MA-327 somewhere available?
I really hope some can help me out.
Thanks in advance
Hans
Click to expand...
Click to collapse
Some please!
What I understood:
You are stuck in a bootloop because you edited the build.prop file, luckily, you made a backup and you know what adb is, and, hopefully, you know how to use it.
How do we solve it?
Well, I need some more information, can you boot into recovery or boot into fastboot mode? If you can, we can make your backup build.prop file active and if that doesn't work, we can just reflash stock ROM, everything will be wiped if you flash stock ROM though.
Hi RAZERZDAHACKER,
Thanks for your help. Yes I can boot into recovery/boot mode (android robot with sign and even can see the menu (Volume + Start). I tried to make an USB connection, but I can not find any driver for this device. Under XP I find a good USB driver, but then ADB want install, in Windows 7 or 10 its the opposite. And even with some not good driver, I see with the command "adb devices": No access, and then 1234567890ABCDEF. Can not find any driver. If possible its no problem to reflash stock ROM, but I do not know how to do this.
I appreciate your help.
Hans
kameraad759 said:
Hi RAZERZDAHACKER,
Thanks for your help. Yes I can boot into recovery/boot mode (android robot with sign and even can see the menu (Volume + Start). I tried to make an USB connection, but I can not find any driver for this device. Under XP I find a good USB driver, but then ADB want install, in Windows 7 or 10 its the opposite. And even with some not good driver, I see with the command "adb devices": No access, and then 1234567890ABCDEF. Can not find any driver. If possible its no problem to reflash stock ROM, but I do not know how to do this.
I appreciate your help.
Hans
Click to expand...
Click to collapse
Thanks for replying, you can boot into recovery which is probebly the most vital thing of this whole process (YaY), in recovery, there should be an option called "apply update from adb", if not, kindly name the options. When you click it, what happens in adb? From my experience you don't need drivers to acces "adb sideload" (as the feature is called).
Yes I see the option.
--------
Now send the package you want to apply
to the device with "adb sideload <filename>" ....
---------
I made the backup build.prop earlier to /sdcard on the device. Maybe that was not a good idea.
Oke whats the next step?
Hans
kameraad759 said:
Yes I see the option.
--------
Now send the package you want to apply
to the device with "adb sideload <filename>" ....
---------
I made the backup build.prop earlier to /sdcard on the device. Maybe that was not a good idea.
Oke whats the next step?
Hans
Click to expand...
Click to collapse
Oh, I thought you had it on the pc, I am not sure but can you do "adb sideload /sdcard/build.prop /system"?
RAZERZDAHACKER said:
Oh, I thought you had it on the pc, I am not sure but can you do "adb sideload /sdcard/build.prop /system"?
Click to expand...
Click to collapse
That don't work. I get the help of adb when I give the command string. Do not know how this will work with a USB connection. How should Windows and adb know when to get the input from?
when i try adb usb, it start the daemon , but then error: closed
adb devices -> 0123456789ABCDEF sideload
Oke maybe a reflash stock ROM. How does this work?
Again I appreciate all your help.
Hans
kameraad759 said:
That don't work. I get the help of adb when I give the command string. Do not know how this will work with a USB connection. How should Windows and adb know when to get the input from?
when i try adb usb, it start the daemon , but then error: closed
adb devices -> 0123456789ABCDEF sideload
Oke maybe a reflash stock ROM. How does this work?
Again I appreciate all your help.
Hans
Click to expand...
Click to collapse
You get error closed because you're in sideload, I realized that you can't move files in adb sideload. If you want to flash stock ROM, download this and move it to the adb folder and type "adb sideload nameoftheimg.img".
Hope that helps
RAZERZDAHACKER said:
You get error closed because you're in sideload, I realized that you can't move files in adb sideload. If you want to flash stock ROM, download this and move it to the adb folder and type "adb sideload nameoftheimg.img".
Hope that helps
Click to expand...
Click to collapse
I will try that of course, but the same image I previously put on SDCARD, inserted it in the bay and dis an update from external drive. Then a message came that hardware was not compatible with the update. I can not find a flash for MA-327 and (again) not for the USB driver. But I will try what you suggest.
I get the error: cannot read 'MA347ENMEG3EV02.img'
Image is 1.744.423.512 size
Hans
kameraad759 said:
I get the error: cannot read 'MA347ENMEG3EV02.img'
Image is 1.744.423.512 size
Hans
Click to expand...
Click to collapse
If you have a sdcard that is large enough for the image (minimum 4gb) you can download win32diskimager. Open win32diskimager and select the .img file. Then, connect your sdcard to your pc and format it to fat32. Then locate it on win32diskimager and write the file. This will take a very long while so please be patient. Once it's done, put it in the hisense and attempt to boot. The android "bios" will go through all the nand memory for a bootable image but since that wont work, it will proceed to check external devices (as far as I know) and once it sees the bootable sdcrad it will, hopefully boot. Once you have booted, don't eject the sdcard, conncect the hisense to your pc and install the necessary adb drivers, then, boot into recovery and hit apply update from adb. Then type adb sideload nameoftheimg.img.
Hopefully that works
Oke. But if it boot from sdcard, then it will not install the img from sdcard?? I though it would.
What are the 'necessary adb drivers'?
And when i give the command "adb sideload nameoftheimg.img, will it get the img from sdcard OR from PC?
So the image is on SDcard AND on the PC? I do not get it (sorry)
kameraad759 said:
Oke. But if it boot from sdcard, then it will not install the img from sdcard?? I though it would.
What are the 'necessary adb drivers'?
And when i give the command "adb sideload nameoftheimg.img, will it get the img from sdcard OR from PC?
So the image is on SDcard AND on the PC? I do not get it (sorry)
Click to expand...
Click to collapse
Not as far as I know, I could be wrong, it could install from it. As far as the adb driver goes this is what I meant, you manually install them. Yes, the image is on both the pc and sdcrad.
RAZERZDAHACKER said:
Not as far as I know, I could be wrong, it could install from it. As far as the adb driver goes this is what I meant, you manually install them. Yes, the image is on both the pc and sdcrad.
Click to expand...
Click to collapse
Hello (again)
It will not boot from the sd card. I formatted it FAT32, used Win32DiskManager to write the .img on it, place the sdcard in the hisense and booted it. Press ON. System will not boot on sdcard. Instead it boot from disk. I see the same logo as before, Hisense Smart. It ignores the sdcard.
Booted it in recovery mode (with inserted SDcard). ADB sideload xxx.img, gave same answer: cannot read MAxxx.img. Other option in the recovery mode like update from external image (i hoped the sdcard) does not work either (can not find any /mnt ect file).
How can I force to boot from sdcard? Is the sdcard now bootable (with win32diskmanager). I used Rockchip Create Upgrade Tool 1.43 also, but this app crash when it want to write to SDcard.
No luck with me till now. Is my device saveable at all? Why does it not see the sdcard?
Hans
kameraad759 said:
Hello (again)
It will not boot from the sd card. I formatted it FAT32, used Win32DiskManager to write the .img on it, place the sdcard in the hisense and booted it. Press ON. System will not boot on sdcard. Instead it boot from disk. I see the same logo as before, Hisense Smart. It ignores the sdcard.
Booted it in recovery mode (with inserted SDcard). ADB sideload xxx.img, gave same answer: cannot read MAxxx.img. Other option in the recovery mode like update from external image (i hoped the sdcard) does not work either (can not find any /mnt ect file).
How can I force to boot from sdcard? Is the sdcard now bootable (with win32diskmanager). I used Rockchip Create Upgrade Tool 1.43 also, but this app crash when it want to write to SDcard.
No luck with me till now. Is my device saveable at all? Why does it not see the sdcard?
Hans
Click to expand...
Click to collapse
It is saveable, can you give me the link to the .img file? The fact that it says "cannot read" might be that the image file is corrupt. Are you sure you are typing the right name? You can do adb sideload then type the first letter (if it is a big letter type it as big for example Achicken, type A, if it is aCHICKEN, type it as a) and hit tap, that will ensure you have the exact name and dont tamper with it as in add .img at the end.
RAZERZDAHACKER said:
It is saveable, can you give me the link to the .img file? The fact that it says "cannot read" might be that the image file is corrupt. Are you sure you are typing the right name? You can do adb sideload then type the first letter (if it is a big letter type it as big for example Achicken, type A, if it is aCHICKEN, type it as a) and hit tap, that will ensure you have the exact name and dont tamper with it as in add .img at the end.
Click to expand...
Click to collapse
Yes I always give first letter tap. This is what I typed
adb sideload M (and then tap) => adb sideload MA347ENMEG3EV02.img
https://docs.google.com/uc?id=0Bwr18Lh81gvJazJXTGFQTnhDSEk&export=download
Its a rar. I unzipped it with 7-zip
I tryed also adb shell. But device is unauthorized and I get eroor $ADB)VENDOR_KEYS not set (even when I deleted .android in my users dir. Do not get any permission question on device also. My hope is still a bootable SDCard and image.
Thanks
kameraad759 said:
Yes I always give first letter tap. This is what I typed
adb sideload M (and then tap) => adb sideload MA347ENMEG3EV02.img
https://docs.google.com/uc?id=0Bwr18Lh81gvJazJXTGFQTnhDSEk&export=download
Its a rar. I unzipped it with 7-zip
I tryed also adb shell. But device is unauthorized and I get eroor $ADB)VENDOR_KEYS not set (even when I deleted .android in my users dir. Do not get any permission question on device also. My hope is still a bootable SDCard and image.
Thanks
Click to expand...
Click to collapse
Might seem crazy but check this out, try with your image then his image(s). Remember, booting from an sdcrad is extremely slow, It can actually take 24hours depending on the speed fo your sdcrad so before trying this I suggest you leave it for a day.
RAZERZDAHACKER said:
Might seem crazy but check this out, try with your image then his image(s). Remember, booting from an sdcrad is extremely slow, It can actually take 24hours depending on the speed fo your sdcrad so before trying this I suggest you leave it for a day.
Click to expand...
Click to collapse
Oke, I will wait for a while. But it seems it just hangs in the normal boot.
Thanks for so far. I will report back after the weekend with hopely good news
Hans
I waited for 48hours but nothing happens. Still the screen Hisense Smart.
So it will not boot from SD card and I can not external mount with adb.
When I go in recover mode I see message:
failed to mount /mnt/external_sd (No such device)
SDCard is raw formatted. Can not browse with Windows SDCard. Maybe it should be wrotten different so I can see /mnt/external_sd
Maybe you have a good idea this week for me.
Hans
Hello!
I have recently bought this phone with installed custom ROM and I wanted to install another one. And then I downloaded the ROM and formatted the phone from TWRP and I just connected it to the PC and there was nothing.. I searched for hours I tried so many adb drivers, usb drivers, etc and I couldn't detect the phone in the ADB powershell nor transfer any files. The only progress I managed to do is side loading it.. The ADB detected it and then I tried adb push (the exact name of the file) /sdcard and after that (error: closed) appeared.. I think the main reason is because before I formatted the phone I didn't allow the usb debuging but apparently you can't allow it from the recovery... I don't have any type-c OTGs laying around.. How in the world am I supposed to transfer the ROM to my phone? Please help me! Thank you!
way2easy said:
Hello!
I have recently bought this phone with installed custom ROM and I wanted to install another one. And then I downloaded the ROM and formatted the phone from TWRP and I just connected it to the PC and there was nothing.. I searched for hours I tried so many adb drivers, usb drivers, etc and I couldn't detect the phone in the ADB powershell nor transfer any files. The only progress I managed to do is side loading it.. The ADB detected it and then I tried adb push (the exact name of the file) /sdcard and after that (error: closed) appeared.. I think the main reason is because before I formatted the phone I didn't allow the usb debuging but apparently you can't allow it from the recovery... I don't have any type-c OTGs laying around.. How in the world am I supposed to transfer the ROM to my phone? Please help me! Thank you!
Click to expand...
Click to collapse
Okey, I just managed to use adb push without side loading just in the twrp and I don't know how to delete the post so excuse me for the spam!
Heyyo, I'm the maintainer of official builds of TWRP for the LeEco Le Max 2.
Usually for TWRP it can sometimes mess up USB mode if the device is plugged into a PC before it fully boots to TWRP.
Windows for some reason messes up the driver install for MTP as well. Usually of this happened you will need to manually go into device manager and select update driver on it and manually select the driver to install like this:
https://photos.app.goo.gl/nRYfpAZ0i50GuM512