hi ,
i have installed a costum rom for my cool 1 c103 android 7.1
then i installed i different twrp so
it blocked when entring recovery mode is block at recovery picture
did not load
i tried to instal correct twrp by apps and root but did not work
Now , phone block and did not load in recover or normal mode
just turn on and stuck
tried adb flashing (cmd adb device not appear even by fastboot devices did nt appear )and by qfile but it seems not detected
all drivers are correct which used in 1st time (when connect phone hear sound of connect & no exclamation mark)
Related
Hello Ive got a bit of a problem actualy a few with my pipo U1 Pro
I installed CWM V6.o.3.1 and rebooted fine, pipo boot image was normal, then i installed from ext SD card Decontaminat V3.1
after install the screen was Split at 2/3 and touch orintation was off with buttons in wrong corners
so i read alot found change in build.prop (ro.sf.hwrotation=270) from 270 to 0 and reinstalled form ext sd card
all it fixed was position of touch screen the image of ui was still split 2/3 and out of rotation.
i reinstalled CWM fron ext sd card reboot ant the cwm recovery is straigt on the vertical and the android shows in center of screen, but ther is a fine line showing where the screen was split in the os.
after reboot the os is still split 2/3 image i have to us the show touch function to navigat the touch field to make thins work
i had TNT pipo u1 pro.img installed before and was rooted worked fine but latly had a few minor problems with it so i desided to chand up a bit.
second problem is i cant get ADB , android studio or rkbatch tools to find my tablet, usb debugging is on, tried the load from adb sideload function in cwm
im running linux mint 17 added udev.rules rebooted every thing many time s swapped usb plugs cords you name it.
as it is the tablet works but the ui is buggered up and touch is off
any help would be verry appricated
mike
May be bricked now ?
I have the pipo stuck in what might be a boot loop?
just says decontaminate with a split screen on bootup shows pipo image then goes to decontaminate screen and nothing.
lsusb shows device { Bus 002 Device 009: ID 2207:0006 }
shows Android device in file manager But Error unable to mount android unable to open mtp device
pushing the buttons '' esc, +vol then power gets nothing.
pushing +vol, power gets nothing
incerting usb and pushing +vol gets nothing
only thing gets anything is push and hold power, CWM is not working cant boot to cwm
tried a bootable sdcard still no boot
was a nice Tablet till decontaminat screwd the screen up
got recovery yeah !!!!
found a way into the cwm recovery through adb.
i added a line into the file here.
/yourusername/.android/adb_usb.ini
its a hidden file added a simple line as root user
0x2207
saved file and rebooted computer.
will post again if i can recover the pipo.
buggered
had total access to the pipo.
i used flash_image to install freaktbs ryley rom for the pipo u1 pro.
now im stuck in a worse position. the kernal.img was not for the pipo.
he was playing with a another tablet and left its kernel.img as kernel.img and had pipo kernel as 1kernel.img
so im stuck with no touch support on the screen and its not defaulted to usb debug mode.
i can see the button acking to allow debug when i connect to usb on linux but no access to touch.
also the rom didnt have any tools for adb installed in recovery /system/bin.
no adb shell support.
only access is adb ls /
to read files and push pull commands.
any ideas on how to edit the default.prob make it stick through reboot and get it to debugg after reboot ?
this sucks MR.RYLEY built a bad rom I was almost into my pipo again.
my guess is the decontaminat rom was using a similar kernel to ryley to get the screen all buggered up.
I was upgrading the current Stock rom on my ZTE Nubia Z5s Mini, I went through the recovery mode to load the new rom and got a message saying that the rom installed correctly, I rebooted the device and now its stuck at the MIUI logo or if I try to load the recovery mode I get the Nubia logo just to load back to the miui logo again. I got the rom from the MIUI site its v5.
I've left the phone for over an hour hoping it was just loading up but no change, the phone heats up and even has a charger screen when plugged in.
Anyway to get back into the recovery mode to load the original rom again or any other way of fixing this? help :crying:
I've no idea how to help you with this but I'm bumping the thread because I know how you feel.
Sent from my HUAWEI Y536A1
I'm trying to flush the rom by using adb but with an issue, even thou my device is recognized as Nubia Z5s Mini in device manager it still gives a driver error "these have been installed" and in cmd adb it does not see the device.
Update : Got drivers for install from Clockwordmod website but it will only accept the drivers if I set the phone as a modem in device manager when installing them, still not recognized by adb using CMD.
Solved driver issue and qusb_download issue, ADB drivers are done through all drives in device manager pointing to the Google USB drivers and select adb interface then run CMD from within the Google SDK program folder in platform-tools to read the device.
Now using emmc but need to generate EMMCBLD.HEX & 7x30_msimage.mbn if anyone can help, I can enter adb using recovery mode but blocked from making changes in fastboot mode, currently in download mode which can see a drive H but need the two files to proceed any further.
first I rooted my device following this http://en.miui.com/thread-30617-1-1.html
then I started super SU and selected normal.
then I opened GLtools i downloaded from here http://forum.xda-developers.com/ ... tools-1-29-t2828630
I installed the GLtools apk and opened it, it asked me to select TEX(DE)coder and install, I did that, super SU asked for root permission, I granted. Mipad rebooted, I opened GLtools nothing changed, it still asks me to install texdecoder, weird, so I installed that again and rebooted and now mipad is bricked and stuck at the MI logo.
I can go into fastboot, however when I tried to use mi pc suite or miflash they do not detect the device so I cant flash fastboot.
when in fastboot device manager shows "android phone fastboot" and it says no drivers are installed for this device, I tried installing drivers like adb driver and fastboot driver etc but it doesnt help.
I am able to boot up the device by using system two, but I need to unbrick system one in case system two gets screwed up.
when in system two, device manager shows android composite device and mi pad and says drivers are up to date. however I still cant anything in fastboot.
I have tried installing android SDK to flash from command prompt but again it doesnt detect hte device and is stuck on waiting for device.
Similar Issue
Without installing TWRP or CWM , I Selected TWRP/CWM in Supersu Binary Installation. Now my MI Pad is stuck at a blank screen
Any help with rebooting the device and flash it
Intall from fastboot
hello,
part 1
I will start by that the LG G3 I got from a neighbor and she did not exactly know what her boys do to the device :angel:
I do not know if the device was in debugging mode and ROOT so I will describe the current situation:
1 If you turn on the device is stuck the logo of LG
2 he can get into a normal recovery, but after I perform Clear / Reset is back to being stuck in the logo.
3- When I try to enter download mode he entered to fastboot mode Started and wait for fastboot Processsing command.
4- My computer installed SRKtool_2.1 droidth and SRKtool_1.0.5_droidth, as well as SDK is updated.
5- I tried to make various adjustments through SRKtool and via fastboot command, the file (*.bin\*.img) send to the device from the PC but faild to write them, and I get messages:
sending laf "okay"
writing laf "failed (remote: flash write failure)
all file have the same masssage.
I try to perform repair to:
A- fastboot mode Started
B- recovery mode
from srktools and I got the same write fail massage !
He's trying to re-write the BIN files taking off from the original rom,
again he can transfer files but does not actually write the on the device,
then the device restarts and then he stuck the logo of TWRP, the expense of battery re-enters the regular recovery mode.
part 2 Updated!
From time to time the device did not enter the FASTBOOT MODE and gets to the firmware update, I install a new ROM, but !!!
the operating system install LGE Android MTP Device driver,
when I flash the rom he stack on 3% and the hardware driver turn to yellow with code 10 (device not work properly).
does LGE Android MTP Device have to be install to do the FLASH ???
the MPT can be damage and that cause the problem ?
the same problem on 2 different PC & OS (xp/7/10) with different drivers for MPT,
after you restart the mobile it returns to FASTBOOT MODE
Hello everyone.
So I decided to update my device as i find out that there is a new default ROM available for my device that is Infocus m530.
I downloaded the ROM and i was flashing it through Software Update Tool (SUT) in Normal mode. The installation process got stuck at 16% for like 10 or 15 minutes so I removed the USB (I know its a dumb move ) . And I rebooted the device and got stuck into a boot loop.
I can access the default 3e recovery mode only but because my ROM was in format ob .nb0 I am not able to Flash it using stock recovery, I can no longer access the FastBoot mode,
When i try to boot the device up it goes into One or two loops and the a windows pop up saying no command. In that window if I press power button the stock recovery shows up.
I tried to flash the ROM again using SUT in emergency mode but the device is getting disconnected automatically. In device manager its showing up as Mediatek Pre Loader USB VCOM for a second or 2 and then automatically getting disconnected and then same No Command menu.
For a minute a new device is also popping in the Explorer which usually contains all the default driver of the phone.
Any way I can recover my Bricked Device
Any help or advice would be much appreciated.
Hi , try to flash this firmware from normal Recovery , once you download rename to update now put firmware inside empty formatted sd card and put inside your phone to start flashing from recovery .
https://www.kriztekblog.com/2016/06...=o67JcQ2b1GjkodlJa9ULilWJwoqb1xZxq6CkVi5D960=
I didn't checked it is for zip or for flash tool so test it first . Good luck .
FIXED
Teddy Lo said:
Hi , try to flash this firmware from normal Recovery , once you download rename to update now put firmware inside empty formatted sd card and put inside your phone to start flashing from recovery .
I didn't checked it is for zip or for flash tool so test it first . Good luck .
Click to expand...
Click to collapse
I already tried it but it didnt work.
So finally I was able to fix the device. The META Mode ain't a myth. Flashed the ROM correctly in META mode and the device booted up properly.