Help! Device without OS only recovery working - Android Q&A, Help & Troubleshooting

Hello! I have a problem with old tablet it is Prestigio multipad 4 quantum 7.85. It is that this tablet doesn't have OS installed so I tried to install it manually with adb . In recovery I turn on ADB update and ADB with command "adb devices" detects it as "sideload" so I tried command adb sideload update.zip (I put it in ADB folder) which contains original software which I downloaded from internet but installation starts and after completion on tablet i see installation aborted. Tablet doesn't have TWRP and as I said only stock recovery is working is there any way to install software to it and will start working?
PS I'm not native speaker but I hope the text is understable

Related

[Q] bricked prime ?

hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
jojo665 said:
hi
i have a issue similar to this thread http://forum.xda-developers.com/forumdisplay.php?f=1465, but just want to confirm
i have a CWM and CM10.1 installed previously but no nvflash,
but during a recently flash i accidently formatted the "system" partition.
I now can no longer boot past the asus logo unfortunately,
and tried the following
1) i can boot into CWM but it only allow flashing from /mnt/sdcard and i dont have any rom in /mnt/sdcard (wiped)
2) i can boot into fastboot (PWR+DWN) and i installed the naked driver v0.72 and it show in device manager -- however "fastboot.exe devices" show nothing
3) if i normal boot (ie stuck on "Eee Pad logo) and install some form of "ADB interface" driver, then i can "adb.exe devices" into it -- but i can push anything onto /mnt/sdard (permission denied)
4) "adb shell" wont work bc of missing "system/bin/sh" hence i cant re-root
5) i can go into APX mode (PWR+UP), but it is not nvflashed sadly
6) i have tried 2 usb cables already, so hopefully not it
Is there anything i can do ... or it is bricked and have to send back to asus for service ?
thanks in advance !
Click to expand...
Click to collapse
First of all try adb push Name_of_Rom.zip /sdcard/
If that does not work try adb push Name_of_Rom.zip /system/media/
If that still does not work then download the correct TWRP blob file from the following link for your bootloader. http://www.teamw.in/project/twrp2/93
The fact that you are on CWM and was using CM 10 makes me believe that you are still on the ICS bootloader but to make 100 percent sure when you first power on the device look at where the "NVIDIA" logo is. If it is bottom center it is ICS, if it is bottom right it is Jellybean. (MAKE SURE YOU GET THE CORRECT TWRP VERSION FOR YOUR BOOTLOADER)
Now rename the blob file you downloaded to twrp.blob. Go into fastboot and type the following.
fastboot -i 0x0b05 flash recovery twrp.blob
This should install TWRP which will allow you to install a rom off an external micro sd.
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
jojo665 said:
turn out it is windows problem -- fastboot device driver (Naked 7.1) is installed but wont connect to the tablet. I ended up installing Ubuntu in order to get fastboot to work.
Once fastboot is working, i able to follow above advice and get my tablet back to functional state.... thanks!
ps: now time for nvflash :laugh:
Click to expand...
Click to collapse
What exactly did you do? I'm trying to extinguish all avenues before I have to RMA my tablet. Thanks for the help!

[Q] Asus Transformer Pad TF103C aka K010

Well, I've used the RootZenFone 1.4.5 version apk method and it worked out for me... problem is, by modding the system I am now getting a boot loop on the main splash and have no adb access. Does anyone know how to force a manual sd update using the downloaded firmware packages and a micro sd card?
My Recovery is stock, so is the Droidboot (fastboot) image, though I cannot get anything through the adb and fastboot commands.
The only time I get something is when i get it into recovery and enable the sideload - pushing a file using the adb sideload command results in a status 0 error / signature verification failed

[Q] "error: device not found" when attempting adb sideload

I'm trying to get 5.0.1 on my watch using the OTA zip file. I've enabled ADB debugging in developer settings, rebooted to the bootloader, gone into recovery mode, selected "apply update from ADB" and got to where it tells me to send the package using "adb sideload <filename>" At this point, I try
Code:
adb sideload 1eac9298ba2d5ae80ba4663518a9882791d23344.signed-platina-LWX48P-from-KNX01Q.1eac9298.zip
but after loading the file, I get "error: device not found"
I'm using an Acer PC with 64-bit Windows 8.1, and before rebooting, Device Manager shows a device under "ACER Device" named "ACER Composite ADB Interface" When I am in the bootloader, another device under "ACER Device" named "ACER Fastboot Interface" is shown. After going into recovery mode, nothing is shown.
Edit: So after more searching, I accidentally ended up on the G Watch R forum, where I found instructions that say you need to unlock and flash the 5.0.1 recovery first. Looks like I'm waiting for someone to post that now.
Bug in the current recovery disables adb in there.
So to work around, you need to root, flash the file to the device, use root privaleges to copy file to secure portion, and your golden. Luckily I already made a script that does that for you!
http://forum.xda-developers.com/g-watch/general/script-roots-updates-watch-to-5-0-1-t2970665

Bricket My tablet after installing chainfire3D adb is also not working

Hi all,
My tablet is stuck at logo after installing Chainfire 3D and i cannot even connect it through ADB as it says Unauthorized or Offline when i type adb devices in command prompt.
Please help how can i recover my tablet back.
I didn't installed any custom rom, no recovery image and also don't have CWM recovery installed on it.
My tablet is rooted and has stockrom on it.
Its a MTK based device named as Qtab V8.
I know there is a thread about how to recover your fone after you installed chain fire but its all based on ADB and i am not able to connect to ADB as i told above so need help.

How to get Android Bootloader Interface with a cube U30 GT C4H

Hi,
I am new in this topic and not a great geek ans please excuse mi for my aprroximative english ! but i am trying to convert an old cube tablet to a domotic tablet. So i have to flash the old rom to a newer like lineageos for example.
So the tablet is an U30GT C4H with android 4.2.2 and the original rom.
I connect the device to my Mac Os and with adb tools (from plateform tools find here) and terminal i wrote adb devices (tablet on) i see the device. OK
When i command fastboot devices, nothing, no line
When i command adb reboot-bootloader, the tablet take off and the screen keep black. With the terminal fastboot devices, no response, with adb devices command > List of devices attached but no more, no device.
With this tablet it is possible to start in recovery mode with power + audio down but with this option i have the android logo and no command. If i take power on no change.
If with adb command and tablet on, i write adb reboot recovery, the tablet restart and the screen see logo android and no command.
I know this kind of topic do not interese a lot of people but i would like use this cube for my house to command domotic (music, heaters etc..). More, i think it's a shame not to recycle this type of device for the planet !!!
Thanx
Fastboot only works if in your tablet's Android's Settings -> Developer options the option OEM unlock got enabled and tablet got restarted afterwards.
i don't see any option OEM in the menu developer
I found that the solution is use slideload protocol. I reseted the tablet and now i get recovery mode. Then i can connect the tablet to my Mac and use terminal with slideload lines. OK
But each time the process failed with rom i found on the net...
Is there an universal rom !!!
Any idea ?
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
jwoegerbauer said:
You don't have to boot the device into Recovery mode:
Code:
adb devices
adb reboot sideload
adb sideload <PROPERLY-SiIGNED-FILE.ZIP>
adb reboot
BTW: adb sideload is meant to re-flash Stock ROMs only.
Click to expand...
Click to collapse
maybe the issue is the rom i doawnloaded ?
it is kasty-cube_u30gt_h-411-111-rooted4_4gb.zip
or
kasty-cube_u30gtc4-441-20131212-rooted4.zip
both failed.
Perhaps i have to unlock the bootloader as you said but i don't know
I'm pretty sure the 2 mentioned ROMs are a Custom ROM. Hence you can't use adb sideload method to flash them. To install a Custom ROM it's required that a Custom Recovery already got installed on device's Android.
I don't find any way to instal a recovery. I had arctools.zip but the app failed to acess to the SD disk or internal storage...

Categories

Resources