Help Tablet h007 does not start, but blinking on android logo

[costarica]

http://www.lightinthebox.com/h007-7...ual-camera-ram-1gb-rom-32gb-gps_p1976346.html

Hallo website, I tried to to post on xda, but there is very difficult. Here I think it`s quite better.
I put the most detailed ever post of my problem, not to be asked questions with no use, and to try to make you think of my problem very clear. Thanks.

The tablet was rooted by kingoroot, but as you know or not, kingoroot, offers root acces, as the 1 service started, when the device is on, but it does not provide general full root settings, as for example when we are in the recovery menu.

I used some kernel tuner application, and I did not make any backups at all. I edited the file with this application, called build.prop, where I change the attribute of user for superuser. In that way, I though, I could get permissions of full root, I did that, because, I could not see my system partition generally, only from total commander, I could see and do whatever I want. After, I rebooted, and the problem started.

I attach here, my device specifications: Which I watched, while I could use the device:

Android system recovery 3e with sw version: alps.kk1.mp1.v2.11. It is on the photo though but with the different name.
MS board: d95b
Mt6582 (Chip)
All the rest is on the photo

I have windows vista 32bit 2 service pack.
MTKdroidTools, the application I tried, 4 different versions, 1, last, and 2 in the years, when my phone was produced. It does not read my phone, saying, it is not present. Though all 4 kind of drivers are installed, even adb device driver is installed and all is perfect, all is connected.

The only thing I can use in this mtkdroidtools is adb terminal. I enter there the following command: adv devices, which shows some number of device connected with sideload.
Something like that:
List of devices attached
01234565ABCDEFG recovery

but at the place of recovery, I have
List of devices attached
01234565ABCDEFG sideload

Then, after reading stack-exchange site, I understand, that now I can enter the system partition to get my build.prop file, to change superuser for user as it was before and to return in back to the device, and get my phone worked. But I can`t do that. Cos as I stated before, the device is rooted only by kingoroot, and I works only as the 1 st. service inside android operating system, but not in recovery menu.
So I cant use the following command to get it right. Cos when I enter any of them, but first of all, I enter: adb usb - it says: error: closed

You can then copy the file off the phone:

adb pull /system/build.prop c:\build.prop

You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:

adb push c:\build.prop /system/build.prop

To work with adb terminal, of course I am in the recovery menu and I enter inside ADB SIdeload Application.
I know how to deal as you see, with this problem, but I can`t get to the file, to the system partition in the whole, cos as I understand, the phone is not rooted.


So guys, let`s see what happens next, I am looking forward to your suggestions.

 

[El Presidente]

Your options with Stock Recovery are fairly limited unfortunately. Do you have a link to the article you're getting your current instructions from please?

 

[costarica]

android.stackexchange.com only from this site I took:

You can then copy the file off the phone:

adb pull /system/build.prop c:\build.prop

You can now edit it in any text editor (recommend Notepad++ because it will preserve the Unix style line endings,) and then copy it back to the phone:

adb push c:\build.prop /system/build.prop

All the rest I found by myself.

 

[El Presidente]

That's the top level site, where's the exact guide you got for your commands from?

I suspect the commands were written with a custom recovery in mind (like TWRP or CWM), if you don't have one of those installed, or the article you were following wasn't written specifically for your device, you might be out of luck. Any chance you can contact the manufacturer and see if they can send you the original firmware?

 

[costarica]

I have already contacted, they told me they were out of stock, so no possibility. All the same, the article, was just about how to use build.prop, no mentions wheter for custom sw or not.

Besides, in my computer, I can see these 2 partitions of android: system and data, but the device is blinking on the start screen with android logo, so I can`t access them, nor mount them, they just show message to insert the disk.

 

[costarica]

so no suggestions? no one knows on 3 famous websites?

 

[El Presidente]

There's nothing to say, without a custom recovery or a way to reflash the stock firmware, your tab/phone is goosed.

 

[costarica]

so, if I find someone who has the same model, what exactly must he send to me? can he do it with some application this backup or what, please indicate from my photo, what exactly must he send to me. thanks. And what the approximate size of this thing.

 

[El Presidente]

Without TWRP or CWM, it would need to be a zip package 0r .img files directly from the manufacturer.

If you wanted someone else to try and send you what's needed, you'd need to get that person to root, install a custom recovery built specifically for that device, factory reset so they're running a completely blank ROM and none of their details/apps/user info is included. Thay'd take a nandroid backup, copy the resulting zip file on to their PC, upload to a file sharing site for you to download, then you'd need to install a custom recovery, push that zip file to your device with ADB, then restore via the options in recovery.

However, if you had a custom recovery you'd be able to get at the build.prop meaning the above was irrelevant.

I really hate to tell you this, but I honestly think you're going to need to get a new phone, sorry.

 

[costarica]

But now I can use this only command like: adb sideload filename and the files are uploading. This TWRP or CWM is needed even to install the original rom?

 

[mikedt]

I think you'll be buying a new tablet mate.

Mike
...your Guide to Chinese Androids

LightInTheBox Ltd.
Diantong Shidai Guangchang, Building #2 Suite D
7 Jiuxianqiao Beilu, Chaoyang District, Beijing, China



/end

 

[hiredgun]

I would try and contact the manufacturer and explain what happened and see if they can send you the zip file like El Presidente mentioned. You don't even have to write the whole problem out again, just copy and paste your opening post here to them. If you are super lucky they will get back to you and send you that zip file and you'll be back in business. Buena Suerte tio, Vin.

Without TWRP or CWM, it would need to be a zip package 0r .img files directly from the manufacturer.

 

[El Presidente]

But now I can use this only command like: adb sideload filename and the files are uploading. This TWRP or CWM is needed even to install the original rom?

A devices stock recovery is good for installing stock firmware and installing OTA updates.

A custom recovery like TWRP or CWM will (amongst other things) allow you to fully use the adb pull and push commands to send whatever you need to your device.

Without an official firmware zip or a nandroid backup (which is a copy of the OS at a given time), you are absolutely out of luck.

I am really sorry, but that's all there is to it.

 

[costarica]

so, official firmware-rom I can put with the adsb sideload in my current situation?

I have already contacted the company, 5 days past, no reply at all.

Having cust twrp or cwm I can install what I want, thought I should not need then to install, cos then I have push and pull function and probably my hidden system partition would be seen, so I can edit my build.prop and return all back, correct? The application with which I did all that problem gave me possibility to make backup of build.prop, but what would it give to me, while I did not have custom twrp o cwm, it is impossibily to make install of one file, correct?

 

[costarica]

I think you'll be buying a new tablet mate.

Mike
...your Guide to Chinese Androids

LightInTheBox Ltd.
Diantong Shidai Guangchang, Building #2 Suite D
7 Jiuxianqiao Beilu, Chaoyang District, Beijing, China



/end

are you the owner of LightInTheBox Ltd??? cos there I have seen, they had this device some time ago.

 

[mikedt]

are you the owner of LightInTheBox Ltd??? cos there I have seen, they had this device some time ago.

Nope... the only thing I have in common with them is the fact we're both in China.

Can't find anything technically useful for a "H007", other than it's a dual SIM phablet, with Mediatek processor. FYI "H007" also model of cheap wheelchair, sold by Amazon China and TaoBao.


BTW the "Alps" in the build number is not the device's manufacturer, they only made the touchscreen component. People have asked about that one before.

 

[costarica]

ok, do not worry, I will finish this thread with El Presidente, waiting for my previous question.

 

[costarica]

El presidente, do not forget me, I wait for your clear short replies.

 

[El Presidente]

Sorry, been at work.

Yeah if you find a version of TWRP or CWM that's compatible with your device, you can push /pull the files you need.

I'm not hopeful but I'll have a Google and see what I can find.

 

[hiredgun]

I just love seeing our tax dollars at work Señor Presidente, if anyone can help him out it's YOU!!!

Sorry, been at work.

Yeah if you find a version of TWRP or CWM that's compatible with your device, you can push /pull the files you need.

I'm not hopeful but I'll have a Google and see what I can find.

 

[costarica]

Sorry, been at work.

Yeah if you find a version of TWRP or CWM that's compatible with your device, you can push /pull the files you need.

I'm not hopeful but I'll have a Google and see what I can find.

pelase, I do not need to wasted your time, write shortly after each question, regards.

so, official firmware-rom I can put with the adsb sideload in my current situation?


The application with which I did all that problem gave me possibility to make backup of build.prop, but what would it give to me, while I did not have custom twrp o cwm, it is impossibily to make install of one file, correct?


The heart of the installation of zipped files for android, is not just like I zip file build.prop on my pc and then install it in adnroid, it`s not the type of that process?

 

[costarica]

update.

 

[El Presidente]

With the stock recovery, you're not going to be able to fix this and there is no TWRP or CWM available for this devices.

It's not as simple as putting the build prop in a zip file either as it needs installer scripts etc to install properly.

I really hate to tell you again, but there's no point in beating around the bush, your device is toast.

Edit - Also removed that stuff about you offering domains etc for someone to fix this, it's not really relevant here.

 

[mikedt]

He's dead, Jim.


Yup, you're definitely going to be buying a new phablet.

 

[costarica]

ok, so original rom won`t give me anything?, so what is for adb sideload, it it works only one side, to upload to device, no use then.

The application is called "Kernel Tuner" . there is one point there, when you click on it, at the top right, you shall see build.prop and you can edit there what you want.

Can anyone enter it and not editing anything to click there on BAKCUP, - it shall make backup for the file build.pro and then to indicate me here, where it was put by the application, on what partition and where in the tree and what type of build.pro it is, like zipped, or how? thanks. Try on any device. I wait.