Related
i cant boot my huawei u8180 into recovery
i rooted it by super one click
when i tried to flash recovery with rom manager premium it restarts then freeze in boot screen
tried to reset my phone from settings ,privacy it also reboot but freeze on boot
i dont know wt to do
PLZ HELP ME WITH THIS ISSUE
plz any one tell me anything i can do with this problem
i cant even reset my phone
plz reply
thanks guys , i solved my problem alone ,, and insalled cyanogenmod 7.2
everything is ok now
how do you solved your problem with huawei u8180? i have the same isue.
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Norpan70 said:
Hi, I had a similar issue and did a reboot in to the CWM by holding power, volume up and the "search button" (?) the right one any way. Then did a wipe/factory reset.
Click to expand...
Click to collapse
So you could only boot into CWM by pressing power+volume+search? The regular way (power+volume) would lock up like it does to me, is that it?
Anyway I tried your key combination and it still freezes...
Codeman666 said:
Sorry to bump an old thread
I'm having the exact same problem.
Rooted the 8180 with SuperOneClick, installed Rom Manager, from Rom Manager installed CWM 8160 version with sucess, and whenever trying to boot into recovery mod the phone just hangs while showing the hourglass icon.
I tried reflashing the CWM and it still hangs
Im still running the stock firmware/rom
Can you share how you solved this problem?
Click to expand...
Click to collapse
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Maeur1 said:
Bug with rom manager, you should try flashing atleast 3 times and then try and go into recovery, happened to me also, just flash again through rom amanager.
Click to expand...
Click to collapse
I already flashed about 5 times and still freezes
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
bk109 said:
Hi,as for the fastboot instructions - I've found this to be a great help in getting adb and fastboot to work on my Win7 x64 installs,so you might want to give it a try. Also,I'm gonna upload in a bit the earlier recovery + recovery manager (if you want to try that before you play around with adb/fastboot) to flash it to your device + the device drivers.
Edit - The link for the file - http://ubuntuone.com/14mi7lUkJelsrNBr4z5Uy2 - 12.5 MB - contains the older recovery (you can still try to flash the newer one first if you want), 2 different driver packs and the aforementioned recovery manager.
Click to expand...
Click to collapse
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Codeman666 said:
Thank you! Im trying recovery manager as I type this, I find it curious it says "Currently installed recovery: unrecognized"
As for the driver, I already had it installed from when I rooted the phone.
EDIT: So I installed the up to date recovery (recovery-clockwork-5.0.2.8-u8160) with Recovery Manager, still unrecognized and still freezes after booting into recovery.
Installed the one you supplied (ClockworkMod-u8160-v0.1) and got the exact same results, unrecognized and freeze
Click to expand...
Click to collapse
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
bk109 said:
In that case you might want to try the doomsday option - fastboot (not really,hell - it's actually rather useful + if you follow that website you also get adb up and working too). As for the 'unrecognized' alert,I remember getting it too once upon a time,but I have to admit - I haven't used the app myself since when I made the jump from the stock 2.2.1 ROM to a custom froyo build,so I can't recall for the moment what I did to fix that error
Click to expand...
Click to collapse
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Codeman666 said:
Will do. Besides the fastboot recovery command what else do I need to do from the phone side?
Does fastboot display any feedback or log about the flashing/installation?
Click to expand...
Click to collapse
Nothing specific -you just have to reboot in fastboot mode (just restart the phone while pressing Power and Volume Down. Windows should chirp and install the drivers automagically - afterwards just use that command discussed earlier and it should flash your recovery without any additional prompts (it should only print out a confirmation of a successful flash) and you should have the CWM ready to go
Edit: I put my device into fastboot mode on a clean Windows install (a Win8 Consumer Preview) and it did autodetect and install the relevant driver without restarting itself
No luck... Now it's driver issues
When booting the phone with either the vol up or down pressed and pluging in the USB my PC isn't recognizing the driver, I used both drivers you sent me.
Initially it's detected as Android 1.0 device, upon fetching the drivers it gets named "Android Sooner Single ADB Interface".
As I refresh device manager it goes back to Android 1.0 with an exclamation mark.
I think it's a driver signature issue, I'll try again in a couple of hours in a different PC
edit:in debug mode I have no driver issues and I can even detect my phone with ADB
Finally!
Tried it in another computer, auto downloaded some ASUS adb driver and installed fine.
Flashed latest CWM recovery with fastboot and now I'm able to boot into CWM!
Thank you so much for your help!
Sry for bumping.
So, i had the same trouble with the drivers. But i just downloaded HiSuite directly from the Huawei Site and these fix my problem with drivers to use adb without troubles . Hope this help someone.
BTW, Thanks bk109!
It did helped me thx man
Sent from my U8180 using xda app-developers app
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 .
Hi!
First off let me say thanks to R_a_z_v_a_n for redirecting me and hope that I'll find my answer here ^^
So I Have this device called HP 7 VoiceTab 1321RA (not with Slate just HP 7 Voicetab), wanting to have a custom recovery then I tried to flash a CWM Custom Recovery for HP Slate 7 VoiceTab because I thought it was the same and ends up bricking my phone. It ends up in a bootloop which only shows HP sign for a few seconds and dead. But I managed to find out that I can access the recovery menu (or so I thought it is), but the options was choosing between Fastboot Mode, Normal Boot, Recovery Mode, and VART Mode.
I tried to enter Fastboot Mode before and tried to access it via PC but somehow I can't find the device by entering adb devices and fastboot devices. Anyways, I have downloaded a stock update.zip for it but not the original KitKat one which I get from the first time I bought it but rather the JB ones. I think by flashing this would help me recover the device but the only problem is I don't know which method should I use to Flash it. Since I don't have the Stock Recovery or ANY kind of recovery at all, I guess I'm stuck. And it won't start to the home page so I can't set the USB debugging options. Please guide me through this >.<
Thanks a lot!
Been fighting with it for 2 days now and still no result came.
So here's the update so far....
I tried on my other device in order to understand how my PC reads ADB and now I kinda gets it. But the problem is now can't get the device to enable USB Debugging because I can't access options at all.
Secondly, since I left it on for the night because charging seems to trigger the bootloop too, now I can't access the fastboot mode like I was last night. And it constantly repeating this sequence: [battery scene with the "charging battery" symbol] > [HP Powered by Android screen] repeated for 2-3 times > [low battery need charging screen] > repeat. And once I tried to connect to the PC, it goes to the same sequence too. When I tried to access the boot options (the screen which displays Fastboot Mode, Normal Boot, Recovery Mode, and UART Mode which I mention in Thread Starting post), it shows the low battery need charging scene and then repeating the same sequence as mentioned above.
I seem to figure out how to fix this but I still can't manage to access the fastboot mode yet. Will give update once I can try to.
Anyone can help me on this?
Thanks a lot!
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
I found my self in a deadlock!
PLEASE HELP :crying:
Could you unbrick yours
What service centre says about that problem i also ran in this problrm but i m trying to go to service centre for that
first off install drivers in your PC as admin
then use the official flashtool to flash ur stock firmware by entering fastboot or flashmode simple as that
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
Dude urs is a mtk device so sp flash tool should do the trick.... Just don't forget to install correct drivers....run both drivers and flash tool as admin..... Tell me when it's solved k
jithinraj said:
@Sunderesh, thanks for the suggestion, however, couldnt get any official flashtool for hp voicetab. Can you suggest one please?
Click to expand...
Click to collapse
That is what im trying. To tell you urs is a mediatek device the official flashtool is sp flashtool
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
try to push the update.zip via adb sideload (Choose "update via ADB sideload" on recovery mode)using adb terminal on PC,as long as your tab can access the recovery mode.remember to backup all your data before u do it.
have a try it's 100% work on me
where I can download update.zip file? anyone can help?
rikicchi said:
Update!
Somehow with a little tweaking and stripping the device, I managed to solve the charging problems. Will update on this once my problem finished.
Jump out from the frying pan and into the fire so they say, I ran into another problem. Finally managed to get into fastboot mode, the devices manager reads it as an Android Device>ROMaster ADB device like the other device I tried to connect while in ADB mode and fastboot mode, but somehow CMD cannot read the device as an ADB device or a Fastboot device like the other device did. I tried to uninstall and reinstall the driver and still nothing happens. I tried to find the usb_driver on the internet and it directs me to the update.zip instead. Trying to update the driver via Computer Management but it says the driver is up to date. Now thinking about making an emulator device based on the HP 7 VoiceTab 1321RA but I really have no idea how to make one. Any one have any idea of what should I do next or can guide me through this? At least until the CMD can read the fastboot.
Thanks a lot!
Click to expand...
Click to collapse
can you explain how did you managed to charge the device??? please its a request......jst help me out :crying::crying:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
I'm stuck with this problem too. The exact problem. Have you found a way to fix it?
I have exactly the same problem with my Huawei Tablet.
If I boot with the original ROM and look in the "/log" - directory with adb shell, there is a cust.log. The contents say, that the specific ROM is not original or factory.
I think even the bootloader is unlocked, there is a kind of signature checking.
EDIT: @Asdforcer: Have you tried to boot the original boot.rom with "fastboot boot" - command?
How to remove FRP on Huawei Y6 TIT U02
Hi,
Since I try to update firmware from HUAWEI website, my phone comes non stop booting (bootloop). Any one can help me how to fix my phone?
Asdforcer said:
Hi guys, i got the Huawei Y6 SCL-L01 phone and i wanted to install a custom rom, so i tried to install TWRP first, but since there wasn't a Y6 version (there isn't a Y6 version for anything pf ) i used the P8 version and it installed but when it rebooted the phone was stuck at a screen that say FASTBOOT & RESCUE MODE. The phone seems to be unlocked according to that screen but the FRP is loocked.
Things i've tried so far
Installed ADB latest version, extracted Recovery Cust System and Boot images from an official stock ROM.
Tried all available drivers from Google TP_Link and Intel for my phone.
The screen i am stuck does not work with ADB commands, the device is not recognized.
Fastboot commands work and it sees the device correctly, the problem is every time i try to flash the images from the stock rom i get FAILED message due to FRP Lock.
Format userdata and cache doesn't work either.
Vol + / - and Power button combinations also have no effect, it only shows that screen regardless of what i press.
I've searched the web and the XDA forums extensively since this happened and tried every possible solution i could find even if it was meant for another device.. no luck.
And here's my question, how can i possibly remove the FRP lock by only using fastboot?
Please somebody help, i am like half a day away from decorating the wall with this piece of ****
PS: I am not able to upload screenshots, sorry about that.
Click to expand...
Click to collapse
Try to unlock your bootloader
could anyone help with a seemingly bricked tab speed 6, attempted to root using kingoroot and it failed causing connection issues to google so i was unable to add a account, after hard reset and booting in to recovery i have wiped the cache and reset to factory, however now the tablet is stuck on checking connection and doesn't go any further with or without sim card.
after searching and searching i have come up with nothing apart from this threadhttp://forum.xda-developers.com/general/xda-assist/stock-rom-vodafone-speed-tab-6-vf-1397-t3329343
it looks as though he is having the same problem.
assuming kingoroot has corrupted the rom and i need to reflash to repair it,
i don't know if it is a generic tablet it appears to be made by alcatel but im unsure.
i also do not know if i could use a firmware from another device or even custom rom, anything will do as long as it doesn't end up in the bin
i also have another which hasnt been messed with and was wondering if it would be possible to back up the rom from it and reflash it to the bricked one, if so could anyone steer me in the right direction
could anyone help me locate as rom and flashing tool that will help
thanks in advance, apologies if this is posted in the wrong place.
You said you had a second one, you don't have to root it, just follow this tutorial and hopefully you should be good to go.
no bootloader
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
inexperience
thanks for the help I am quiet inexperienced but determined so any help pointing me in the right direction would help thanks
facerolla said:
hi thanks for your reply however upon backing up the other tablet, it had still not solved the problem does that tutorial back up the Rom or just system files I created the backup.ab and used adb recovery to no avail...., however, I gave up on this method and was going to use a custom recovery on the the working tablet to back up the rom, however when I tell adb to reboot to the downloader it just reboots the tablet there seams to be no downloader on either tablet, so even if I had the rom it appears I could not flash it via the downloader as I can't get to it, nor sd card as there is no option to flash it, it's really bugging me now as it's obviously only soft bricked, any more help would be greatly appreciated thanks in advance also to add fastboot lists the device but when I tell it write the recovery it says waiting for device
Click to expand...
Click to collapse
What command do you do to tell adb to reboot to download? What command to you give fastboot to flash the recovery?
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
I don't know if download mode is accessed differently I've found this post that seems to Suggest hold volume up and down then connect until battery charging appears http://forum.gsmhosting.com/vbb/f272/vf-1397-a-2047715/ this is for unlocking it seems, but don't seam to be able to get it to work, earlier I removed root with kingoroot from kingoroot app, also to no avail and rooted again both root removal and rooting were successful but still tablet stays on the checking connection screen when rebooted, I was hoping the removal may of fixed the issue but no...., I was thinking if I could get back custom recovery on it I could do the same to the working one I have begrudgingly so I could back up the working ones rom and use it to flash the bricked one, but I don't really want to risk bricking that one either, but was considering finding another rom from another model the same chipset and flash it with that but obviously no download mode means I can't do it..
if it's any help The recovery mode states android system recovery <3e>
LMY47V release keys
reboot system now
wipe data/factory reset
wipe cache partition
power down
enable adb
they are the only options,
again thanks for all your time and effort
facerolla said:
hi thanks for the quick reply im ujsing adb reboot-bootloader , it reboots the tablet and then greats me with the vodafone start up logo then asks me which country im in, as for attempting to flash with fastboot ive tried fastboot oem unlock to unlock the bootloader ( says waiting for device) ive also tried adb push c:\adb\backup.ab ( doesnt seam to recognise the psush command as it cycles through all available commands , and attempted to flash recovery with fastboot flash recvovery cwm.zip ( says waiting for device) adb reboot sideload just reboots the tablet same as adb reboot bootloader, thanks for all your help.., ikt is really bugging me i appreciate your time.
Click to expand...
Click to collapse
You can't always unlock the bootloader via that command and you'll need to have the bootloader unlocked to flash a custom recovery, if you can find stock images on the web you can flash them via fastboot.
---------- Post added at 12:44 PM ---------- Previous post was at 12:36 PM ----------
Also to restore an adb backup you do "adb restore filename".
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
facerolla said:
unfortunately there is no stock image anywhere on the Web, is there a good app I could use to save the rom from the working tablet without rooting, really don't want to risk rooting the working tablet
Click to expand...
Click to collapse
Hello! Remember this?
Also to restore an adb backup you do "adb restore filename".
Click to expand...
Click to collapse
Did it work? I see you left a "thanks" so I assume something happened.
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
facerolla said:
hi, I give up on the tablet, I've been asked to see if I can give it another go, but don't know where to start, I still have a working one but no idea how to get the rom from the working one to the bricked one. thanks for the help you gave me to begin with.
Click to expand...
Click to collapse
I have a couple tricks up my sleeve and that is, you know how you said when you ran adb reboot bootloader? Run adb shell instead and it should give you a command explorer, from there, type "su" and report results, you should see either a root request on the device or a hash sign in the coommand shell.
Just a quick question
Did you ever manage to get it working if so how did you go about doing it as i attempted to install a custom boot animation and it appears to be stuck in a constant boot loop as such i'm not really sure what to do with it or if it is savable. Any response would be helpful. Thanks.