I have a great problem, the system on bq E45 don't start.
When I switch on the phone, start the bq splah screen and it stop to the second screen with ubuntu and the dots that change color. Now it is past 3 hours and the situation don't change.
I can't use adb (device error) to flash the rom, I can use only fastboot but i don't know where I download the img files to flash and which ones!
Help me please!
Solved
install all packages to install ubuntu touch (see ubuntu wiki);
switch the uphone in recovery mode and connect it to pc with ubuntu;
open terminal in pc and type command adb devices;
if the device respond, type the command ubuntu-device-flash touch --channel=ubuntu-touch/stable/bq-aquaris.en;
if the device not respond, download recovery-krillin.img;
reboot the uphone in fastboot mode and flash the recovery image;
reboot the uphone in recovery mode and type the command ubuntu-device-flash touch --channel=ubuntu-touch/stable/bq-aquaris.en --device=krillin;
good fun :good:
Related
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
robboy said:
I spent the whole of yesterday trying to add MoDaCo custom rom. from this post http://forum.xda-developers.com/showthread.php?t=552591 The first of my problems was that I couldn't get the right driver which now seems to be fixed now comes up as - ADB Interface -HTC Bootloader.
So this now means that when i go to fastboot I can load cyanogenMod (system recovery) by typing fastboot boot cm-hero-recovery.img
However none of these commands below in the CMD work. All i get is error: device not found
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
Any ideas please
Click to expand...
Click to collapse
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
It does change to fastboot usb on red. The only thing I can think of is do you have to install the sdk as I couldn't see a setup app. I just have all the files on the c dive. Will try skipping the first step when I get home
you dont install the sdk, just unzip it
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
jackdaniels_lee said:
Still sounds like a driver issue.. have you installed HTC + the SDK?
Restert ur handset into bootloader, hold power + back, then plugin the USB cable.. "FASTBOOT" (,In the red square) shoud change to FASTBOOT USB..
Skip the "adb shell reboot bootloader" and go straight to the next line and boot the recovery image via fastboot
should be plain sailing from there
Click to expand...
Click to collapse
Grrrr still no joy. Just device not found. Im deleting all files that I have downloaded for drivers sdk etc and try and start again from scratch.
Do I need to partion my SD card before I do this as i have been having probs with that as well.
jackdaniels_lee said:
thats right just the unzip, sorry, the drivers come with the SDK, if you still have no sucsess, do a Controll pannel > system >device manager then scan for device changes, if it finds the device select to install drivers and point it to the SDK folder
Click to expand...
Click to collapse
Done that as well. If My device runs fastboot this should mean the drivers are correct.
robboy said:
Done that as well. If My device runs fastboot this should mean the drivers are correct.
Click to expand...
Click to collapse
yes if u succeed to enter fastboot, it means it had recognised the phone? are u using windows 7 by the way? cause u have to download the precise drivers for the OS u r using whether x64, win 7 ....
I seem to remember having problems with this until I enabled the USB debugging mode in the options somewhere.
As for drivers, I'm running Windows 7 x64 and the x64 Vista drivers did the job fine.
Here is what I stand.
I have soft bricked my TF201 and I am trying to restore it using ADB per the recovery thread.
I am stuck in CWM recovery boot loop.
When I entered bootloop USB Debugging was not enabled and I dont have a computer that had/has the TF201 drivers previously installed.
Computer system is Windows Vista.
When the USB plugs into the computer it is recognized as "Transformer".
I have downloaded the drivers from the Asus site, from ADB repositories, and from other sites proportedly hosting drivers that work. None of those drivers have worked when attempting to manually install them (Device Manager > Update Driver Software).
How can I install drivers to get ADB to recognize my device if I cannot enable USB Debugging?
First i would install the recovery using fastboot again. Download drivers (link) and install it, download new cwm touch recovery (link), Restart your prime by holding the volume down button, wait, then press down to switch to the usb symbol, then press volume up. Now you are in fastboot mode. Enter the following command at the terminal or command prompt window : fastboot -i 0x0b05 flash recovery (path to cwm recovery img)
Thanks, Ive got USB working and was able to flash to CWM Touch Recovery.
Now when I try to push (adb push update.zip /sdcard/) I keep getting: Protocol Failure
This happens every 3rd or 4th time I try to push. The rest of the time I get a daemon failure.
Any suggestions on how to push a ROM so I can install it? (I dont have one on the internal SDCARD any longer)
hi everyone,
I'm coming from this thread http://forum.xda-developers.com/showthread.php?t=1834761
I have been stuck for more than one week now and i didn't find any solution.
My problem is that I'm currently stock in a clockworkmod recovery boot loop on my Asus Transformer Prime without adb/fastboot connection:
1 - I had install CM9 stable on my Transformer Prime, after a wide data and then send throw "adb push" the CM9.zip,
2 - I reboot by CM9 in recovery mod to install Gapps,
3 - I install the Gapps zip,
4 - I ask to clockworkmod to reboot,
5 - Since then I'm in a clockworkmod recovery boot loop without adb/fastboot connection (witch used to be working),
If kown how can I get adb/fastboot connection back to be able to find my device with the adb command " adb devices " and then be able to send this command => " dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 "
Thank you for your understanding,
Kind regards,
Adb and fastboot are two different things... Fastboot is obtained buring booting process with vol down pressed, then not selecting recovery with volume up. So you should have fastboot access.
In this case I would suggest to fastboot flash TWRP (see on their website for instructions) it will perhaps fix things or at least give you adb access.
If you use cwm take the old 5.8.2.0 modded for not looping with reboot to recovery feature, or stay with twrp.
I would look at the following thread for unbricking the TF201:
http://forum.xda-developers.com/showthread.php?t=1514088
Sounds like you might fall into Option 1a.
I was having your same issue but it was because I rebooted into recovery from the reboot option on the CM10 rom. In any event, I couldn't get adb to work or recognize my device no matter what. I then decided to use my macbook pro. I can tell you that using adb on a mac is much easier as you don't have to download the drivers or sdk, just the platform tools. Here's a link: http://forum.xda-developers.com/showthread.php?t=1387527. I know this may not help if you or someone you know doesn't have a mac, but it saved me.
I am having a REAL BUGGER of a time with my Xiaomi Redmi Note 3 Pro (Snapdragon)!
1. It is not recognized by ADB in Fastboot mode.
2. I suspect it shipped wit a vendor ROM, and I'm trying to flash latest Official MIUI Global Dev (Marshmallow) ROM, but I keep getting errors in MI Flash (screenshot attached).
3. I want to Flash TWRP, BUT ADB isn't working, AND I cannot get to the download page for the cracked bootloader.
4. Seriously considering Resurrection Remix ROM, instead, but most of the above issues still apply.
I am NOT new to custom recoveries, flashing ROMS, ADB etc, BUT I am dealing with a new PC (Windows 10 Home, 64 bit, like my old (dead) laptop), and I'm new to this device.
PLEASE HELP. (Quite frustrated)
Fastboot won't recognize adb commands you have to use fastboot.
What you can try is booting into emergency download mode and using my flash to flash it from there. I think it's " adb reboot edl" while the device is on with USB debugging or using the mi updater app ( tap the three dots I think).
I think that this is not the correct section for your question, and i dont know the procedure that you follow but try to follow this procedure:
-Connect the phone at pc with USB cable
-Make sure that debug mode and OEM unlock was abilitate in dev settings
-Copy twrp.img in adb folder
-Shut down the phone and press power botton and - vol buttons for enter in fastboot mode
-Run this commands by terminal open in adb folder
fastboot devices
-If fastboot recognize correctly the device run this command
fastboot fash recovery nameoftwrp.img
-After reboot the device with this command
fastboot reboot
When the phone reboot press immediatily vol + for enter in twrp
Good luck
GOT IT! FINALLY!
-I finally got ADB to connect, and was able to enter EDL through ADB.
-Re-downloaded ROM from web.
-Re-extracted.
-FLASHED SUCCESSFULLY!
-SETUP COMPLETED SUCCESSFULLY!
-YAY!
(I think the original download was corrupted, somehow.)
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...