Hi guys, I have one Kinpad i600, and last week try update, using
wrong rom( I get on this forum).
Now my tablet is bricked, cant update using recovery mode (I alread try put anothers rom version on SD CARD and nothing).
Cant acess for ADB too, in Windows I dont locate yet correct drivers for this tablet.
I just install Ubuntu on another PC, and try install ADB too, but no sucess on access tablet.
Someone have one idea to resolve my problem??
Sorry for bad english
You need to enter recovery mode.. i dont have a kinpad so idk how.
Once you are in recovery, you can then maybe fix it.
I used Rom Manager on stock rooted Nexus 4 to download the cyanogen 10.1 nightlies wiped and everything but after I flashed it loads the rom but keeps giving me setup wizard has stopped and cant get past that, I want to load another rom on the phone wipe and flash to fix but I dont know how the computer wont recognize my phone as storage so I can, can somebody please give me some info step by step on how to fix?
This is assuming you have the adb/fastboot drivers working...
When you have the phone connected to your PC open a command prompt and navigate to where you stored your ADB/Fastboot EXE's.
Type "fastboot devices" without the quotations. Does your phone list the serial number?
If so you can flash the stock ROM and start all over. But before we get into that the above confirmation is needed.
Really need help with this still havent figured it out, I just need to push a rom to my phone so I can flash it.
Not sure if you saw my post above... please confirm.
Hi guys
I`ve got a major Problem Here. Please help!!
Me and a friend wanted to update my rooted Galaxy s4 from The unofficial to the official Kitkat Firmware. But The update failed. We tried again but still no succes. I didnt have enough space on my SD card. So I did a factory reset, installed twrp and let Odin install a small custom Rom. Odin succesfully installed it but Then I got stuck in The Boot screen. Probably I didnt turn on USB debugging
After days of surching The web I found out that I could change The rights for USB debugging over ADB tool. But i get stuck on The <su> command after entering <ADB shell>. The command cant be executed or something like that.
I then noticed that the root had gone with the factory reset. I installed that and now my PC (adb) wont recognize the phone anymore.
What should I do? Im still quite a noob so please dont critizise me if I missed something obvious.
Should I use ADB or is there a better sollution?
Please please help.
Hope that theres a sollution.
Keep posting
illias9 said:
Hi guys
I`ve got a major Problem Here. Please help!!
Me and a friend wanted to update my rooted Galaxy s4 from The unofficial to the official Kitkat Firmware. But The update failed. We tried again but still no succes. I didnt have enough space on my SD card. So I did a factory reset, installed twrp and let Odin install a small custom Rom. Odin succesfully installed it but Then I got stuck in The Boot screen. Probably I didnt turn on USB debugging
After days of surching The web I found out that I could change The rights for USB debugging over ADB tool. But i get stuck on The <su> command after entering <ADB shell>. The command cant be executed or something like that.
I then noticed that the root had gone with the factory reset. I installed that and now my PC (adb) wont recognize the phone anymore.
What should I do? Im still quite a noob so please dont critizise me if I missed something obvious.
Should I use ADB or is there a better sollution?
Please please help.
Hope that theres a sollution.
Keep posting
Click to expand...
Click to collapse
Do you have a custom recovery? Try to install it. I recommend CWM 6.0.4.6.
Later that, flash any flashable rom(remeber: correct model). Later flashing, reboot.
Hy Guys,
I have tryed to put the rom from Gionee Elife E7 on my Blu life pure XL. The installation occurs everything okay, but when i try to install the recovery, my phone reboot, and never more turn on again... I only can see the Gionee logo, but then shutdown after that. When i try to connect on the PC, just two drivers are showed to me:
-Gionee HS-USB Diagnostics (COM5)
-Qualcomm MMC Storage USB Device
I can enter in ADB mode, but i have no way to acess the internal storage...
Any help will be grateful...
sampadf said:
Hy Guys,
I have tryed to put the rom from Gionee Elife E7 on my Blu life pure XL. The installation occurs everything okay, but when i try to install the recovery, my phone reboot, and never more turn on again... I only can see the Gionee logo, but then shutdown after that. When i try to connect on the PC, just two drivers are showed to me:
-Gionee HS-USB Diagnostics (COM5)
-Qualcomm MMC Storage USB Device
I can enter in ADB mode, but i have no way to acess the internal storage...
Any help will be grateful...
Click to expand...
Click to collapse
when u installed the rom did the phone start up properly?
This look's bad man.
Try power on your phone then
Plugin into your computer.
Open adb then type adb devices
When your device is listed type adb reboot recovery
If IT doesn't boot in recovery mode then You should try flashing again the rom.
Something should work.
Sent from my E7 using Tapatalk
have you fixed it? perhaps i can help
if you've got fastboot (power + vol -)
you can fastboot (sort of like an adb) flash some system images and get your phone getting recognised by gnqc
you need :
ADB
boot.img from blu rom
system1.img from blu
right click on folder where adb and files are (they need to be on same folder for faster tipying)
write
fastboot flash system system1.img
fastboot boot boot.img
after that unplug phone, you need the drivers for blu, change cable from pc port and reconect to see if now it's recognized as a pure xl and check for the drivers.
It should install 2 com ports (hsusb, nmea) 1 adb, 1 modem and 1 storage
that is what i did to mine, hope it works on yours
dzamora said:
if you've got fastboot (power + vol -)
you can fastboot (sort of like an adb) flash some system images and get your phone getting recognised by gnqc
you need :
ADB
boot.img from blu rom
system1.img from blu
right click on folder where adb and files are (they need to be on same folder for faster tipying)
write
fastboot flash system system1.img
fastboot boot boot.img
after that unplug phone, you need the drivers for blu, change cable from pc port and reconect to see if now it's recognized as a pure xl and check for the drivers.
It should install 2 com ports (hsusb, nmea) 1 adb, 1 modem and 1 storage
that is what i did to mine, hope it works on yours
Click to expand...
Click to collapse
this helped me but now i have another problem phone starts up then reboots sometimes it reboots in the middle of starting up i can get into stock recovery but i have no idea what to do now
jetboss said:
this helped me but now i have another problem phone starts up then reboots sometimes it reboots in the middle of starting up i can get into stock recovery but i have no idea what to do now
Click to expand...
Click to collapse
Ok now, you can use GNQC and flash the rom and that will completely restore your phone
NOw if only i could find the blu rom for a 16gb blu
dzamora said:
Ok now, you can use GNQC and flash the rom and that will completely restore your phone
NOw if only i could find the blu rom for a 16gb blu
Click to expand...
Click to collapse
funny thing is i did that and thats whats causing this boot loop i got into recovery after reset and still nothing
is there anything i can push using adb to solve this ?
jetboss said:
funny thing is i did that and thats whats causing this boot loop i got into recovery after reset and still nothing
is there anything i can push using adb to solve this ?
Click to expand...
Click to collapse
perhaps a stock recovery.img can help
dzamora said:
perhaps a stock recovery.img can help
Click to expand...
Click to collapse
ok well im going to try pushing the elife 7 stock recovery and see what happens
tried that all it says is installation aborted .....
You have to to try this,that is how i have unbricked mine today.
power off your phone.
prepare your gnqc so you only have to press download when needed.
power on your phone then conect fast to PC ,then press download.
If IT doesen't leț You ,pres again and just try to see If IT works in different situations.
is a long shot but this is how i unbricked mine today.
fastboot doesen't work on this device,so You can't push anithing. i don't know hou this people are doing that.
If this metod doesn't work You shold try format system and data via adb . and after that gnqc should work.
Muresan01 said:
You have to to try this,that is how i have unbricked mine today.
power off your phone.
prepare your gnqc so you only have to press download when needed.
power on your phone then conect fast to PC ,then press download.
If IT doesen't leț You ,pres again and just try to see If IT works in different situations.
is a long shot but this is how i unbricked mine today.
fastboot doesen't work on this device,so You can't push anithing. i don't know hou this people are doing that.
If this metod doesn't work You shold try format system and data via adb . and after that gnqc should work.
Click to expand...
Click to collapse
He can't use GNQC because his phone's drivers arent insatlled, gionee blocks com ports, and fastboot does work on this device, you just got to flash it, i've been using it several times
A thing to notice is when you want to acces phone storage when phone is bricked You have to poweroff your phone and keep pressing power and volume+ untill some errors start appear in windows.
then You have acces to phone memory and You can paste anithing for later flash with recovery. You must Be very carefull not to format partition when asked !!!!!!
i have bricked my gionee 32 gb several times and always been albe to restore it so,no need to panic,some method should work for You too ,just have to find the right one.
And also,my phone is a rebrand of gionee from Romania,called Allview x1 xTreme,just like life pure Xl and i haven't encountered any problem with usb drivers, just used the one gionee provided. So this mai Be the case for You, i hope i am not wrong with this one.
Com ports are only closed in android 4.4 kitkat so If he didn't update he should Be able to use gnqc.
also You must observe that phone is recognised differently by windows deppending in wich state your phone is. powered off,recovery,or on bootloop. So that's why o have said that gnqc may work but You have to find that state when he is recognised the way that gnqc wants.
Sorry for long post i Hope those observations will help you.
Sent from my E7 using Tapatalk
I finally got it to work using the phone right now to send this message
jetboss said:
I finally got it to work using the phone right now to send this message
Click to expand...
Click to collapse
Got a couple questions would appreciate if u could help.
1. How did u root the blu xl i have both the 16g and 32g
2. Did u install custom recovery in it?
3. Links to downloads plz ...
Thanks in advance
Sent from my SM-G900H using XDA Free mobile app
noblelinux said:
Got a couple questions would appreciate if u could help.
1. How did u root the blu xl i have both the 16g and 32g
2. Did u install custom recovery in it?
3. Links to downloads plz ...
Thanks in advance
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
I can give you some info on root and recovery, im also hoping for someone to be able to extract the 16blu life pure xl rom since the only one is for 32 gb
for root you can just use Vroot and then after installinh busybox and supersu you may erase it, for the recovery i've got the files just send me a pm and ill mail you the link
dzamora said:
I can give you some info on root and recovery, im also hoping for someone to be able to extract the 16blu life pure xl rom since the only one is for 32 gb
for root you can just use Vroot and then after installinh busybox and supersu you may erase it, for the recovery i've got the files just send me a pm and ill mail you the link
Click to expand...
Click to collapse
I sent u a pm hit me bak and ill help u with the 16gb pure xl
Sent from my SM-G900H using XDA Free mobile app
Came bak to chek if any reply i broke both my screens on the blu life pure xl 16g amd 32 gb im now on galaxy s5 but still im gonna replace the screens and use the phones for something idk most likely android dev practice
I just need info on how to extract the rom from the blu
Thanks in advanced
Sent from my SM-G900H
Where files link to download?
jetboss said:
I finally got it to work using the phone right now to send this message
Click to expand...
Click to collapse
Hi can you tell me how did your phone started back, i am also stuck on reboots , recovery is working fine , any OS/ ROM is giving me reboots all the time..please help
honestly it was a long time ago and i cannot remember what i did except it was a windows xp pc software wouldnt work on 7 and i used stock rom not the one from blu
[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom
Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed
Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:
Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*