Related
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?
So I installed "Hairybean 2.3 (4.2.1) Bootloader & Recovery.zip" onto my TF201 Transformer Prime but like a complete noob I left the ""Hairybean 2.3.zip" ROM itself off the internal storage. Now the tablet won't boot to get the ROM copied over. Even better, the microSD port on the tablet was previously hosed by my brother hammering in a card practically sideways.
How in the world do I get the ROM accessible to the tablet, or get the hairybean bootloader removed? How bad off am I?
xandroid_prime said:
So I installed "Hairybean 2.3 (4.2.1) Bootloader & Recovery.zip" onto my TF201 Transformer Prime but like a complete noob I left the ""Hairybean 2.3.zip" ROM itself off the internal storage. Now the tablet won't boot to get the ROM copied over. Even better, the microSD port on the tablet was previously hosed by my brother hammering in a card practically sideways.
How in the world do I get the ROM accessible to the tablet, or get the hairybean bootloader removed? How bad off am I?
Click to expand...
Click to collapse
While you are in TWRP you have access to ADB.
Make sure you have the drivers installed (look in device manager if there is an exclamation there or if you have a device)
Then you would need adb on your pc and put the rom.zip in the same folder as it and do adb push romname.zip /sdcard/
You should then be able to access the rom from the internal when it has finished copying.
There is an ASUS Android Devices\Android ADB Device listed under Device Manager, but when I try adb push "Hairybean 2.3.zip" /sdcard/ I get an "error: device not found".
I'd actually tried this earlier and forgot to mention it in the original post, add it to my big list of boneheadedness. What obvious bit am I missing here?
xandroid_prime said:
There is an ASUS Android Devices\Android ADB Device listed under Device Manager, but when I try adb push "Hairybean 2.3.zip" /sdcard/ I get an "error: device not found".
I'd actually tried this earlier and forgot to mention it in the original post, add it to my big list of boneheadedness. What obvious bit am I missing here?
Click to expand...
Click to collapse
type adb devices and tell me what output you get.
Sorry, yet another thing I should have listed. adb devices comes back with "list of devices attached" then a blank line. So I'm definitely doing something wrong.
Here is the adb and fastboot I use and also a link to the drivers.
http://www.androidfilehost.com/?fid=22962010882834442
OK downloaded both, when I pointed windows at this driverset the tablet now shows as "ASUS Android Composite ADB Interface". Extracted the ADB-Fastboot file and ran adb devices again, same result (no device listed).
Now what am I doing wrong? I feel like every single step I take I run into another catch-22.
xandroid_prime said:
OK downloaded both, when I pointed windows at this driverset the tablet now shows as "ASUS Android Composite ADB Interface". Extracted the ADB-Fastboot file and ran adb devices again, same result (no device listed).
Now what am I doing wrong? I feel like every single step I take I run into another catch-22.
Click to expand...
Click to collapse
Try restarting the PC.. If still broke try a different USB port. Preferably one on the back.
Multiple reboots and trying every USB port on my rig proved fruitless.
So I punted and moved this process over to a win7 laptop (was working on a Win8 desktop, if it matters) that had never been connected to the tablet, started fresh.
adb devices sees the device!
adb push "Hairybean 2.3.zip" /sdcard/ successfully completed copying the file over!
Starting the install now. Thank you so very much for the assist, I'd hit so many roadblocks I was about to surrender!
xandroid_prime said:
Multiple reboots and trying every USB port on my rig proved fruitless.
So I punted and moved this process over to a win7 laptop (was working on a Win8 desktop, if it matters) that had never been connected to the tablet, started fresh.
adb devices sees the device!
adb push "Hairybean 2.3.zip" /sdcard/ successfully completed copying the file over!
Starting the install now. Thank you so very much for the assist, I'd hit so many roadblocks I was about to surrender!
Click to expand...
Click to collapse
No problem mate. Glad you got it sorted :good:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Thanks mate! You just saved my day.
I had the exact same problem and couldn't get sideload to work in TWRP 2.7.0.0 on Nexus5. But simple "adb push..." worked.
this doesn't work
thank you very much, you saved my day,too.
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man... you just saved me a ton of trouble. Tried this on the Nexus 4 and works like a charm! :good:
just wanted to say thanks!
for some odd reason, my twrp (even though its the latest for my nexus7 grouper) had the same flashing no status error)
used the kill, usb, and push commands to copy over 3 different zips (rom,kernel,gapps) and it all copied over ready to flash
thanks!
23468
seriously thanks mate! work like charm :good::good:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Same Issue
jacktackle said:
for me it copies the small files but my rom is 1gb plus it gives me the error 'protocol failure' can some one give me a helping hand here?
please?
Click to expand...
Click to collapse
Three days and All I can do is flash a recovery. Insertcoint goes though and says it's installed but nothing but HTC Screen
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
Thanks man. You're lifesaver
Awesome, this worked for me too
HELP
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
mahmoud hakim said:
I have htc one s somthing wrong happend turned the storage from 16 giga into 48 mega byts i cant get back my storage what to do please help me* i still can push roms but i cant because there is no storage what to do
Click to expand...
Click to collapse
Can you ruu. Then do a factory restore. That should reset the partition
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
derekokelly said:
This does not work for me. Firstly, I tried installing Cyanogenmod by putting it on my internal SD card, then booting to recovery and installing the zip, and this did not work. So I tried to sideload it and got the error " * failed to write data 'protocol fault (no status)' * ". I don't know what to do. I've also tried the same with Paranoid Android but I get the same errors. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Exact same problem I have, any suggestions?
try changing to usb 2.0, usb 3.0 sometimes not working with adb command.
much love
Thanks for saving the day voxigenboy!!! I love you man. lol
And for those that simply can't get their stupid computer to recognize the LG drivers... PDANet wins with whatever voodoo they freaking use!
Thanks for your help, rescued my evening!
voxigenboy said:
so.... I screwed up & wiped my dna. no recovery img, nothing left on it a side from recovery.
i have team win v2.5.0.0
been trying to use adb sideload to install another rom. my pc recognizes the phone & i get adb running. been trying this method:
going to "advanced" in recovery, then:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)
every single time, it keeps saying - *failed to write data 'protocol fault (no status)' *
anyone else experience this and know how to fix it?
FIXED!!!!!!!!
--------------------------
Rather then do "sideload", I just stayed in 'Advanced' and performed:
adb /kill-server
adb usb
adb push (romname) /sdcard
it successfully copied the rom to the sdcard folder, then I was able to install the rom just fine.
Click to expand...
Click to collapse
I'm sorry, that's a bit confusing.
So are u suggesting to "sideload" by:
adb /kill-server
adb usb
starting up "adb sideload",
adb devices
adb sideload (romname)?
Waiting for your response.
Zenfone 5 a501cg (India) (WW)
Stock Recovery
This didn't work for me but I found this other way of passing the archive to my phone :
https://www.youtube.com/watch?v=Z3SpI7m7mFI
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