Hello everyone,
I have a typical problem - my device does not load, because it loops with android logo. It does that because i edited vold.fstab incorrectly, but have the correct lines copy in comments within the file. Problem is i don't have any idea how to enter recovery mode ( if one exist at all ) on the device! I tried most of popular combinations and nothing worked - the device always start to load normally, and loops. Most solutions to this situation is via abd, but abd does not see the device ( i guess because it's not started/not in recovery mode ).
Is there a way to access root or force the recovery ?
The device has label TR976V12 and 2012.06.06 on the board, but it's propably N90 model. I could use any help with making this work again.
Also i'm running windows 10 and i have some issues to make it work in fastboot mode...
Edit:
Device is running Android 4.2
ABD see the device as 0123456789ABCDEF
I managed to get the device to recovery mode by holding VOL+ and plugging in power supply.
Any help in finding vold.fstab to edit it back to the original is more than welcome !
Related
Hi all
first of all I apologize if this is not the right place to put my inquiry in, but I could not find the specific forum for this device.
I have serious problem with this android mobile phone. it is pretty good phone very useful with dual sim function one of them is 3G with WiFi Hotspot but the problem that I have rooted the phone with superoneclick and I have installed a lot of apps in it modifying some language files then when I restart the phone to let the changes take effect then the mobile keep restarting for infinite. Tried to get in to the recovery mode by using Call Button+Volume up+Power but the screen became blank. I spent the whole day searching the the internet to find the solution but with no clue. the problem the device is new and not supported that much in the public forums. could not find Stock Rom. Huawei website and bulletin was not useful.
is there any way to do it through USB or sdcard and How?
thanks in Advance
I am still trying to find a solution...
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
bl88drg said:
if you need it, I attached the original recovery dump to this post.
then you just need to get "fastboot" and then (after preparing your device for fastboot):
"fastboot flash recovery recovery.img" (on a command line opened on the same folder where "fastboot" is)
or you can probably do it too on Linux if you prefer. if it is possible, you'll find the way for it on Google.
also, to access fastboot mode is POWER+VOL_DOWN (not volume up or a 3 key combination) and recovery is POWER+HOME (which you probably already know).
the system dump I can't send because I never made a dump.img of it and I am currently having a bootloop problem (I'll probably have to flash the original rom from a friend).
Click to expand...
Click to collapse
Hi, Can you help me and upload the boot img. I accidentally erase the boot partition.
Many Thanks.
Hi,
after some complications with the partition mapping on my tablet i finaly extracted the boot.img created a custom boot.img. Now want to flash it back using adb, fastboot or flash_image. Afaik flash_image isnt supported, get some errors "error scanning partitions"....
So i tried to flash with adb / fastboot, but it is required to boot to bootloader mode.
I tried many key combinations on my tablet (power button, home, volume keys) and apps to boot it into bootloader mode but was not successfull yet ("adb shell reboot bootloader" and Quick Boot App from Play Store).
I´ve got an Allwiner A10 Tablet with T15A_V5 Mainboard and 1GB RAM (like the goclever a103 tablet). Also known as (same hardware):
- Manta MID06
- Point of View Protab XXL
- Goclever A103
- Storex eZee'Tab 10C
- Coby 1042
- Yarvik TAB464
Any idears how to get to bootloader mode or flash the img back?
Ty.
*push*
easier to get anwsers for apple devices than getting feedback here... wtf?!
You don't reflash these A10-based tablets from bootloader mode. AFAIK they don't even have a bootloader mode.
You reflash them from your PC using the Livesuit program, with the tablet connected over USB.
The tablet has to be put in a specific mode (FEL mode) in which the screen will remain dark and a different USB device will be detected by the PC (Livesuit comes with a driver for this).
To put the tablet in this mode :
- turn in off completely (not just standby mode) and disconnect the USB cable
- start the Livesuit program, and select the firmware image (.img file) you want to flash
- hold the Volume- button on the tablet and while holding it, connect the USB cable to the PC
- while still holding Volume-, make a succession of quick press and release on the power button (at least 5 or 6 in my experience)
You'll hear your PC detecting a new USB device.
- release the button
- make a force installation of the driver that came with Livesuit
A popup should appear asking if you want to do a forced format. Choose yes, then flashing should begin (progression bar)
livesuit wont install
i downloaded livesuit but when i try to install it blinks out and nothing happens can i get help please ? im so close to fixing my Eglide Pro III
Please HELP!
Yesterday I flashed my Odys Xelio (Allwinner A10) with CWM. After booting in a working state, I restarted in Recovery too full whipe and whipe dalvik, I installed gapps ans the compatibility.zip also from CWM.
After that I got stuck in a whitescreen. I can not access anything, not even CWM recovery anymore. In win 8 I only could see 1 to 2 undefined devices (should be a problem with the device AND a driver issue).
In Linux I could see a device in adb yesterday and could put it into "adb reboot recovery". Still whitescreen on the tablet, but I could push a recovery file with adb to the /sdcard/. Rebooting didn't bring me to another state.
Today I am not able to connect via adb. It always tells me "List of devices attached" and an empty list.
Display should be okay, no cable issue or sth. else. I really hope someone can help. Perhaps theres a way to JTAG the devices or there is a trick with pressing some buttons and using the USB cable...
BTW: While booting into CarbonRom the first time, the button-behaviour was strange or even totally not working. Perhaps that's a point?
THX in advance
EDIT: Now, after playing around with a needle into a "reset-hole" I finally found a way to see the device in adb. How do I go on!?
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Turn off the phone --> Run minimal ABD and fastboot as admin--> just write the command for recovery install (don't hit enter yet)--> press volume + and volume - button and connect the phone to pc via usb--> now hit enter and voila. Your phone will boot in recovery.
Click to expand...
Click to collapse
Good luck!
anyone?
f4780y said:
Sorry to hear about your bricked phone. I can't help specifically as I don't have a Lenovo, but having a search around XDA there seems to have been some success reported in the following thread:
http://forum.xda-developers.com/showthread.php?t=2597590
See this post - http://forum.xda-developers.com/showpost.php?p=52013378&postcount=412
Another post in that thread suggests:
Good luck!
Click to expand...
Click to collapse
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
hientran41 said:
i tried this aldready, but my phone is locked bootloder so that method is no help. Thank you for your support anyway.
Click to expand...
Click to collapse
OK, but did you look at the second link there, to the specific post in that thread? It suggests a process for locked bootloader, which is why I thought it might help...
Anyhoo, I hope you manage to get it fixed somehow!
Is anybody have the droidboot.img file from the VibeZ K910 dualsim, pls upload it for me. i cannot find it anywhere.
I look into the second link as well. that method for user have a working phone but locked bootloader and want to downgrade.
Ah, OK. Sorry I couldn't help.
u fix your phone?
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
hi do u fix your phone?
Geguniukas said:
hi do u fix your phone?
Click to expand...
Click to collapse
i bricked also
dunno what to do..
---------- Post added at 12:13 AM ---------- Previous post was at 12:13 AM ----------
hientran41 said:
I have a VIBEZ K910 with locked bootloader after upgrading to version 4.4.2. Now it's bricked. Cannot enter test mode with the combination Volumn - and Power button. I think the droidboot.img is damaged. Cannot enter recovery either. Anybody can help me unbrick the phone? Pls:crying:
Click to expand...
Click to collapse
did you fixed the phone?
lenovo k910e 4.2.2 bricked after TWRP for 4.4.2 installation
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Solution ( k910 bricked )
Ok here is the solution even if your device ( k910 dual sim ) is completely bricked as was mine.
I was stuck in Lenovo logo with no success in finding right and working drivers ( windows 7 64x ) and i was not able to to get in recovery official ...everything was just - somehow - deleted...
I had locked bootloader **** and was not be able to flash cmw in working mode ****
There was nothing for me that could recover my phone even if the "hard" way with QPST or miflash etc
So....after 3 days....find this solution and hope this will help you because it is soooooooooo easy finally!
Steps:
1) Download lenovo driver ( i think it is useless in fact but ok....just run it you dont have anything more to loose )
https://www.dropbox.com/s/frbpz16udrefoit/LenovoUsbDriver_autorun_1.0.112.exe?dl=0
2a) Download and install Minimal adb
https://www.dropbox.com/s/uvngsu4vz4hvsky/minimal_adb_fastboot_v1.1.3_setup.exe?dl=0
So now you have to use the right recovery image ( this file has to be inside minimal adb folder )....so here it is:
https://www.dropbox.com/s/ge05m1fe8n4qgb1/recovery.img?dl=0
2b)
Download this ROM ( this worked for me - with other i did try i did get an error )
http://www.needrom.com/download/lenovo-k910-vibeui-2-0/
prefer the last updated version ( 1501 )
Put this rom in the same ADB folder and renale zip in VIBE1411.ZIP ( in order to be easier later )
3) Turn off the device open Adb and write : fastboot boot recovery.img ( to have it ready )
4) Push volume + $ volume - at the same time and AFTER connect with usb to your pc - At the time the device will vibrate HIT ENTER in ADB
This will flash the recovery and after 1 minute device will open in a recovery screen with an adb update option ***
SELECT THIS adb update OPTION !
Your device kow it is ready to flash the new rom ! ( you will realize that everything is right from many usb beeps you will hear )
5)In adb console write : adb sideload VIBE1411.ZIP
This will take a little ....after that your device will reboot ! Dont panic if for a few minutes it will stuck in lenovo logo....
IT IS NORMAL AND YOU HAVE TO WAIT!
Hope this will help you.....please feel free to tell me if this worked for you.
C u
Same thing happens to my lenovo vibe z k910
buzzbuzz1 said:
Hi , this is my first time on the site , so forgive me if ive posted this in the wrong place.
I briked my Lenovo k910e running 4.2.2 rom with google apps purchased off Aliexpress.
What i did was run the flashrec.exe file for TWRP , but not until too late did i realise it was for 4.4.2 instead of 4.2.2.
Now i cannot boot the phone , TWRP was successfully installed and operational , but after about 20 reboots TWRP flash screen is stuck on the TeamWin logo and not accessable.
Ive tried mostl sugestions on this site and others without luck.
I can get the phone recognised with fastboot only after these commands ;
cd downloads
cd fastboot
adb devices
and it seems i may be able to push files to my device.
Is there a working link to the k910 OEM rom k910_ss_s_2_040_0109_131226 someone could direct me to.
All the links i have found so far are corrupted. Is there a way of repairing the TWRP recovery i have in the phone now.
Am I correct in assuming I have to install the OEM factory 4.2.2 ROM to wipe TWRP and istal Lenovo recovery ?.
Any help would be so appreciated. Thanks
Click to expand...
Click to collapse
After running twrp recovery it operates 3-4 times but now it flashes on twrp screen and screen goes blank and again flashes . I am unable to on it and as it shows only light and lenovo logo after that blank screen . Please help me in this. Its only detecting in adb recovery not any other mode.
lenove vibe Z k910 locked and stuck in logo
hello all
I ve done every word and many other tutorials but still the problem the same:
adb devices give just nothing
but fastboot devices gives the device
the driver is installed correctly detected in devices of the computer
here is the response for :fastboot boot recovery.img:
~/Desktop/lenovo]$ fastboot boot recovery.img (master✱)
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
FAILED (remote: Locked)
finished. total time: 0.538s
thanks for everyone to help
Boot into recovery under bricked condition
Today I bricked K910 after reinstalling GMS apk.
The phone hanged at boot logo.
Nothing can be from here.
I decided to take this risk.
I removed the back cover and disconnected the battery terminal.
After that I plugged back the terminal.
Several tries by power button and volume down to get into the recovery mode. All failed.
Each time it hanged at boot logo.
I have to redo the battery terminal unplug sequence again.
This is correct method to get into recovery mode.
Press power button and volume down till the Lenovo logo appears.
Move the power button finger to the position of the " Home " of the touchscreen position.
Hold till the recovery menu appears. Choose factory reset to erase the phone.
There was two lit small icon below. Make your choice.
The phone will be erased by reset.
Reboot after the process.
I solved my phone bricked problem.
Hope the method will solve your problem.
Good day to all K910 users.
my vibe z cannot access the recovery mode (PWR + VLM DOWN), it only vibrate. If turn on only stuck at Logo. Please help .
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.