Not sure where to post this, as I'm quite new here, but here it goes.
Every time I try to flash the CWM in my M2 d2306 I get a screen black with blinking background led at reboot.
Then, I re-flash the kernel and bootbundle, and everything works okay. But then, no CWM.
What must I do in flashtool? I connect via fastboot, then click in Flash kernel with the .img provided in one of the topics here.
Also, I'm sorry for my newbieness... I used to own a WP 7.8 ....
Power + volume up button press(10 seconds) and off the phone
Open flashtool select firmware wait the connect phone message press volume down button connect pc and wait ending firmware flashing
ishakcez said:
Power + volume up button press(10 seconds) and off the phone
Open flashtool select firmware wait the connect phone message press volume down button connect pc and wait ending firmware flashing
Click to expand...
Click to collapse
I'm really sorry if I'm mistaken:
Well, maybe I'm just too dumb, but... ain't this just the same as I said...? Let me try this again:
1. I install CMW. Then, when I reboot, it gets the bootloop.
2. I, then, install the custom VIVO firmware for my Xperia M2 d2306 (realized that I just need to flash the kernel again). The phone DOES boot.
3. I can't enter recovery mode anymore
Context:
The real problem, actually, is that after all this work, ignoring that the recovery mode got broken, I try to uninstall some system apps, like the VIVO BS, Google Magazine, Xperia Lounge, etc... But after I close the Titanium (or NoBloat Free) the shortcut of the app is still there. It does not launch, giving an stop error or something, but if I reboot, it gets fully restored.
I thought it had something to do with the superSu not being installe properly, so I tried to boot into CMW to reinstall SuperSU., thus beggined my loop with the flash->bootloop->flash-bootloop... :crying:
You have system as writable? When i update from 4.3 to 4.4 i had root but not system as writable so i can't to uninstal apps. TB was showing to me that is uninstaling apps but after reboot they were still instaled. So if you don't have system as writable you can't install CWM and have bootloop.
Sent from my D2303
Dzepar said:
. So if you don't have system as writable you can't install CWM and have bootloop.
Click to expand...
Click to collapse
That seems to be the case, thanks! I'll try to figure out how to make /system writable.
Thank you again
I'm on phone but there was tread for that. Search it ?
Good luck.
Sent from my D2303
Root acces possibly lost.
I guess I let something very important slip...
I was trying to fix system, but couldn't write to sony_ric/enabled, so I've redone the rooting, and just after installing SuperSU, via CWM, I got the following error when I tried to power off:
Code:
Root access possibly l
THIS CAN NOT BE UNDO
- No
- Yes - Fix boot (/syst
As you see, it's missing some characters, so I had no idea of what it said. I've googled it a little and soon found that there may be some workaround,
like using TWRP.
Question time:
1) But can we, users of M2, have a stable access to TWRP (didn't found anything saying no, but neither saying yes)?
2) Does it have something to do with my su binaries been messed up?
3) Does it have something to do with the bootloop?
4) Everytime I install the kernel of my custom firmware, I can't access CWM anymore. Can I fix this or is this the default behavior (or both:fingers-crossed?
PS: I followed this topic: [TUT] Fix Mount System in Kitkat After Root
Two questions answered
tkgcmt said:
Question time:
1) But can we, users of M2, have a stable access to TWRP (didn't found anything saying no, but neither saying yes)?
2) Does it have something to do with my su binaries been messed up?
3) Does it have something to do with the bootloop?
4) Everytime I install the kernel of my custom firmware, I can't access CWM anymore. Can I fix this or is this the default behavior (or both:fingers-crossed?
PS: I followed this topic: [TUT] Fix Mount System in Kitkat After Root
Click to expand...
Click to collapse
Well, I guess I found the answer for two of my questions.
A2) Aparently I was using the Google Play Store version, that is known for not being able to update de binaries, and such...
A4) Using the flashtool removes the root somehow. I don't know how I got it working the first time, though, but now none of my apps given root access works. I'll try this: http://forum.xda-developers.com/xperia-m2/general/root-d2303-kitkat-18-3-c-0-40-locked-t2929893
update
Just an update.
The method of Engineer91 didn't worked out for me, as OTA fails to update me to 4.4.2
I've tried to flash the kk with flashtool, ticking (removing from the flash) only the kernel (as seen in androidclub, but then I got a bootloop again.
I'm running out of ideas... does anyone knows what can I do to fix the system not being able to be mounted as writable in the KK (Android 4.4.2)?
Related
Hello,
I need some help to get the new ICS update. I have a TF101 (no G), serial B80, with firmware HTK75.WW_epad-8.6.6.23.
Previously I was on 8.6.6.19 and used razorclaw to root it. Then I have done the wipe data, and installed 8.6.6.23.
When I boot with Power and Vol- then Vol+ to enter RCK mode I get the green android guy with exclamation mark.
When I boot with Power and Vol-, then Vol+ I get 2 options: Wipe data and android cold boot.
I used some apps to test if the device is root and they say no.
Sorry for my english, but it's not my main language.
Any idea to fix this?
The 8.6.6.23 is firmware for the 3G model. You will not see OTA since ICS is not released for G model yet.
You can try to manually install 8.5.6.21. You could also try rooting and installing cwm recovery and flash the ICS ROM
Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model
mantorrix said:
Thanks for the answer. I've searched around and it seems that I can't get back to 8.5.6.21.
When I try to install it I get the android guy with exclamation point.
I guess I have to wait for ICS on 3G model
Click to expand...
Click to collapse
Easiest way is to root, install CWM recovery and flash an ICS ROM. Either the stock rooted ROM or one of the many custom ROMs
I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!
Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]
DreadKing said:
Hi,
may i hook in here, i've got a similar problem:
i TRY to get in adb mode, but it doesn't work as expected:
i used this thread initially (ASUS Transformer Root ToolKit V7.1 Universal (Windows) | 2011-09-22), i downloaded the toolkit, connected my turned off tab to the pc, booted via Power + vol up, it got connected to windows and i installed the drivers. so far so good. BUT: if i start adb server and use adb device, i dont get any devices listed... i cant do anything. And when i use this nvflash method with the download.bat file, i get an error and the usb connection vanishes... i dont have any further ideas what to do. but i can boot afterwards normaly to 3.2.1, though i dont get any updates
any hints? Thanks for reading anyways
thanks, DK
[edit] i have the version HTK75.DE_epad-8.6.5.21-20111216 installed [/edit]
Click to expand...
Click to collapse
What you did was put your tablet into APX mode. That's only good if you're doing NVFLash not ADB.
To use ADB just have yourtablet on like normal with USB debugging turn on
Hi,
thanks for your fast reply, you are right. i got my adb device id when beeing in the os, so this works. but, trying to use nvflash/Brk's Asus TF RootKit over apx, i got the initial connection, but when i want to flash it looses the connection or dies or something... no idea what
you got any hints how i can come back to a clean version, which is upgradable?
thx & best regards,
dk
this is the program output btw:
Creating backup of current boot and recovery img
this should take some time... please wait
Loading Bootloader to pad... please wait!
Starting...
Error! Could not load bootloader.
Click to expand...
Click to collapse
alexlarson011 said:
I was in a similar situation. The ASUS recovery did not work for me either and I couldn't figure out how to install CWM. There is not a lot of help for noobs with B80s and with all the methods out there it was a challenge to find the correct one. Here's what I did:
1. If you are not rooted, follow the instructions in http://forum.xda-developers.com/showthread.php?t=1427838 to get rooted. I had updated to the .21 firmware, and at that point, the nachoroot method is the only option. I had some trouble connecting ADB, but eventually I got it to work. This was the most difficult part of the process.
2. Install CWM. I was having trouble with this using the ASUS recovery, and I think it has to do with B80 models. I found the app in this thread http://forum.xda-developers.com/showthread.php?t=1346180 and it is amazing. If you are rooted, it installs CWM even on the B80 versions. The custom recovery will allow you to install any rom.
3. Download the option B ROM from http://forum.xda-developers.com/showthread.php?t=1514658. Place the zip on your SD card. This rom is the ASUS stock ICS firmware with root. Contrary to what some have said--I noticed a huge difference with ICS!
3. Backup all your user apps and data with Titanium Backup (optional). Do not back up system data, just user apps if you want to keep them.
4. Open your recovery. Shut the tablet off, and boot into recovery by holding down the power button and the volume down button until you are prompted to boot into recovery by pressing volume up. Pressing volume up should load CWM.
5. Wipe and then install! To wipe, select "wipe" on the recovery menu. Then wipe all data, cache, and dalvik-cache. To install, select install zip from SD card and find the zip file you downloaded in step 3.
Best of luck!
Click to expand...
Click to collapse
Thanks! This worked for me. Thank you sir! Everything worked fine and I'm now on ICS!
followed exactly alexlarson011's instruction and voila - it works! thanks a lot!
best regards
-dk
Hi, I need help. I flashed the DoomsDayRom on my Xperia J ST26i. I followed all the steps and it went well until I wanted to flash a new rom. I found out that I could not access CWM on my phone even after doing the Vol. up button when there's the purple light. In fact, there was no purple light! There was only a blue light before the phone booted up. After that, I deleted the .zip file from my SD card and tried again. It was the same. Except this time, the error message "Unfortunately, the process android.process.acore has stopped.". That popped up every time I closed it and I couldn't do a thing. Please help me!:crying:
I downloaded the rom from here: http://forum.xda-developers.com/xperia-j-e/development/doomsday-rom-jlo-stock-based-t2636164
Try installing CWM from PC again.
If you still can't go to it, you may also try some xposed module (I am sorry, I forgot the name) which gives you options to reboot (even to recovery) when you try to turn off your phone by pressing and holding power button.
If that still doesn't work, you gotta flash your phone bro.
Thanks, but...
maxzeroedge said:
Try installing CWM from PC again.
If you still can't go to it, you may also try some xposed module (I am sorry, I forgot the name) which gives you options to reboot (even to recovery) when you try to turn off your phone by pressing and holding power button.
If that still doesn't work, you gotta flash your phone bro.
Click to expand...
Click to collapse
Thanks, but I've tried installing CWM again, but to no avail. I've also downloaded ROMmanager and tried to reboot into recovery, but the phone just hung. And what do u mean by flashing my phone?
Shuame
Death1792 said:
Thanks, but I've tried installing CWM again, but to no avail. I've also downloaded ROMmanager and tried to reboot into recovery, but the phone just hung. And what do u mean by flashing my phone?
Click to expand...
Click to collapse
Im using Shuame to re-unlock my bootloader and I will then root it...
By Flashing your phone, I mean using Flashtool which uses ftf files to install stock ROM into the phone. Its similar to Sony Update Service or PC Companion repair method, but doesn't require you to download firmware each time you flash.
P.S. Press Post Reply instead of Reply to avoid quoting yourself
Hi,
I am new to this site and fairly new to rooting and stuff and need assistance with my Sony Xperia S (LT26i). If i am not in the right pace for this please point me in the right direction. I have installed a custom rom and custom recovery which let me upgrade from 4.1.2 to 4.3 which was working fine then when I flashed a different custom rom after that to get 4.4.1 I lost access to my custom recovery. The main issue is that I need help with changing the custom rom I have installed, for some reason I can no longer boot into TWRP or CWM (using power + vol up), the phone simply boots normally and skips the whole process therefore I cannot flash anything. I have looked for hours over the net on how to get into recovery but could not find a solution.
I also assumed that when installing custom recovery and custom roms that you would need to be rooted but when I check with Root Checker it says that I am not. So any assistance would be great
Bizzmagizz said:
Hi,
I am new to this site and fairly new to rooting and stuff and need assistance with my Sony Xperia S (LT26i). If i am not in the right pace for this please point me in the right direction. I have installed a custom rom and custom recovery which let me upgrade from 4.1.2 to 4.3 which was working fine then when I flashed a different custom rom after that to get 4.4.1 I lost access to my custom recovery. The main issue is that I need help with changing the custom rom I have installed, for some reason I can no longer boot into TWRP or CWM (using power + vol up), the phone simply boots normally and skips the whole process therefore I cannot flash anything. I have looked for hours over the net on how to get into recovery but could not find a solution.
I also assumed that when installing custom recovery and custom roms that you would need to be rooted but when I check with Root Checker it says that I am not. So any assistance would be great
Click to expand...
Click to collapse
try to root again or if it wont work, back to stock and start from begining
Paget96 said:
try to root again or if it wont work, back to stock and start from begining
Click to expand...
Click to collapse
Thanks for the feedback, because I am quite new to this stuff can you tell me what the best and easiest way to root the phone is? I have tried the root toolkit but it wont work with my rom i have atm. I cant access my recovery either so how would I go about getting back to stock rom?
Bizzmagizz said:
Thanks for the feedback, because I am quite new to this stuff can you tell me what the best and easiest way to root the phone is? I have tried the root toolkit but it wont work with my rom i have atm. I cant access my recovery either so how would I go about getting back to stock rom?
Click to expand...
Click to collapse
you have all here
follow this,and back to stock, then root again, install cwm or twrp recovery, and install what ever you want
http://xperiafirmware.com/8-firmware/13-sony-xperia-s-lt26
Do you know of any other site where I can get the firmware from?, when I try and extract the file after I download it it's corrupted. I have tried multiple times with no luck.
Bizzmagizz said:
Do you know of any other site where I can get the firmware from?, when I try and extract the file after I download it it's corrupted. I have tried multiple times with no luck.
Click to expand...
Click to collapse
witch android do you want?
---------- Post added at 01:54 PM ---------- Previous post was at 01:51 PM ----------
Here is 4.0.4
https://docs.google.com/file/d/0B_d8uWGbkaetLThpYzEwZUh5aTg/edit
steps:
how to install the newest Android 4.0.4 for Sony XPERIA S LT26i
a) first of all, check your firmware version (if you already have the newest one, you do not need this tutorial)
b) download and install latest Flashtool from here (mirrors Google Drive or Mega)
c) download also latest Android 4.0.4 (mirror) for Sony XPERIA S LT26i
d) paste the ftf file downloaded in step c) to folder „Firmware“ included in the XPERIA Flashtool
e) open the XPERIA Flashtool, click on flash and choose downloaded firmware, than click ok. Important - if you do not want to delete any data of your phone, just uncheck flashing userdata.sin file. All data will remain in your phone, but sometimes it can cause additional troubles. So it is better (and I recommend that) to do the backup of your personal data, than proceed with clean instalation and then restore your personal data.
f) turn off your phone and when Flashtool shows pop up window, connect phone to PC with holding volume down button
g) after few minutes all is done and your phone gets the new firmware
Here you got 3 ways to update good luck
http://androidteen.com/xperia-s-lt26i-update-to-android-4-1-2-jelly-bean-official-firmware-6-2-b-1-96/
Ok so I successfully downloaded the firmware file but I got an error when using the flash tool, I have attached the log if you can maybe help me out with what went wrong.
Bizzmagizz said:
Ok so I successfully downloaded the firmware file but I got an error when using the flash tool, I have attached the log if you can maybe help me out with what went wrong.
Click to expand...
Click to collapse
The clue's in the error message - you don't have the required drivers installed.
There's a directory named "drivers" under the main flashtool dir. Run flashtool-drivers.exe and install the appropriate drivers. I think "Common Drivers Viskan Board" is the one you need. I ended up installing all of them to get it to flash (which took ages).
Ok so I got it to work, all I had to do was hold down the vulumn down button for like an extra 5 seconds while it began to flash
Thanks for the help, I appreciate it
Bizzmagizz said:
Ok so I got it to work, all I had to do was hold down the vulumn down button for like an extra 5 seconds while it began to flash
Thanks for the help, I appreciate it
Click to expand...
Click to collapse
work??
dont forget to press thanks
Hello again
So I have successfully rooted the device and installed TWRP but as before I cannot seem to get into the recovery mode, when I boot the phone with "power and vol +" it doesn't boot into recovery but instead there is a quick glimpse of what I think is the recovery mode (I cant actually see it but something happens for a split second) but it flashes past way too fast then goes to the normal Sony logo and continues booting normally. I have tried this like at least 20 times in the last 2 weeks and have researched other ways to boot into recovery but I can't seem to find anyone with an answer. Do you know what could fix this? Or is there a way to boot into recovery using a computer?
Bizzmagizz said:
Hello again
So I have successfully rooted the device and installed TWRP but as before I cannot seem to get into the recovery mode, when I boot the phone with "power and vol +" it doesn't boot into recovery but instead there is a quick glimpse of what I think is the recovery mode (I cant actually see it but something happens for a split second) but it flashes past way too fast then goes to the normal Sony logo and continues booting normally. I have tried this like at least 20 times in the last 2 weeks and have researched other ways to boot into recovery but I can't seem to find anyone with an answer. Do you know what could fix this? Or is there a way to boot into recovery using a computer?
Click to expand...
Click to collapse
use this to reboot into recovery
ang go to reply, because I dont see you post
https://play.google.com/store/apps/details?id=pl.qbanin.reboot
i am not responsible for damaged devices though this may not happen warning Please make backup of system after installing recovery MTK tools for some odd reason due to lack of proper drivers wont detect ur phone
Hello to all BLU vivo iv users this thread is for gaining root access after updating your blu vivo iv to 4.4.2 usually it can't be rooted properly u can get root via recovery install method but root explorer and other root apps will not get proper su access but it won't work or will fail constantly to complete system operations meaning u can't edit system at all!!!:crying:
I made an insecure boot.img with more adb access seeing that it does not have much developer options in settings it still wont but this boot img will allow proper root.
first u must install Carliv recovery from here not my work this is for Gionee elife s5.5 but vivo iv is same device so it's safe tested myself :http://elifes55.blogspot.com/2014/07/guidegionee-elife-s55-cwmroot-required.html
use mobile uncle from market and update recovery choose recovery.img first item at top of the list the downloaded recovery img must be in base of internal storage do not place in any folders!!!
after that reboot to recovery vol up + power scroll with vol keys power to select scrool to install zip then scroll down to install from internal sdcard choose "bootimgADB.zip" wait for install to finish wipe dalvik and cache (ps when doing this it takes about a min or two idk why just dont panic and think your phone is stuck)
after that procedure continue to rooting using Vroot / root genius
Vroot: http://vrootdownload.org/
Root genius: http://www.shuame.com/en/root/
download root checker from market to check for root
Screenshot
https://www.dropbox.com/s/1iyfst24ye3bm1s/Screenshot_2014-08-21-10-48-26.png
update
please install supersu.zip after boot img flash in recovery then root over with root genuis
Thanks a lot for that information. There is not a lot of help aroudn for Vivo iv owners!!!
I have a problem before i reach 4.4.2, as the OTA update will not install correctly.
I have a rooted phone, with recovery installed.
I downloaded the OTA update, installed it, then it booted to recovery and gave the following errors:
CWM automade 10.07.20014 00:34:23
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can’t mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Any idea what this means? I tried unrooting my phone, and installing the OTA update again, but it gave the same error. I have emailed Blu, but i'm sure they will be unhelpful. I've tried googlin, and other people (with different devices) with similar errors from OTA updates say you cannot install the update.zip directly from recovery otherwise it gives:
assert failed: getprop("ro.product.device" == "**********" || "ro.build.product" == "*************"
E:Error in /sdcard/downloaded_rom/***********.zip
...errors. Which from some peoples replies also gets their phone stuck on bootloop, so I don't want to try that.
Any ideas how to get this OTA kitkat update installed? Did yours update normally (with.without root/recovery)?
Thanks in advance
James666PKR said:
Thanks a lot for that information. There is not a lot of help aroudn for Vivo iv owners!!!
I have a problem before i reach 4.4.2, as the OTA update will not install correctly.
I have a rooted phone, with recovery installed.
I downloaded the OTA update, installed it, then it booted to recovery and gave the following errors:
CWM automade 10.07.20014 00:34:23
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can’t mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Any idea what this means? I tried unrooting my phone, and installing the OTA update again, but it gave the same error. I have emailed Blu, but i'm sure they will be unhelpful. I've tried googlin, and other people (with different devices) with similar errors from OTA updates say you cannot install the update.zip directly from recovery otherwise it gives:
assert failed: getprop("ro.product.device" == "**********" || "ro.build.product" == "*************"
E:Error in /sdcard/downloaded_rom/***********.zip
...errors. Which from some peoples replies also gets their phone stuck on bootloop, so I don't want to try that.
Any ideas how to get this OTA kitkat update installed? Did yours update normally (with.without root/recovery)?
Thanks in advance
Click to expand...
Click to collapse
did u try choose zip from internal then update.zip but still try to get the update.zip for me
yes it would install with root but not custom recovery i kept my stock recovery cuz i knew blu would be releasing KITKAT btw amigo OS ruined KITKAT its like if it didn't update at all
hmm u have the answer at the start custom recovery may not install an official rom update though i may be wrong but if u can get the update.zip where it downloaded on your storage i can poke around and design it to flash via custom recovery
please in future do NOT!!!! install custom recovery before official update it gives probs
since u have the recovery there is an miui rom u can try to install from gionee elife s5.5 make sure u backup though its based on 4.2.2
thanks very much! I will upload the update.zip. I really only need kitkat for an app I am trying to use (which only works on 4.3 and newer) so the MIUI rom won't be of use to me.
If you could have a poke around and create a custom recovery that will boot it, that would be amazing, I will upload the update.zip now. I would forever be in your gratitude.
Also is there a way of removing custom recovery from the phone?
---------- Post added at 09:24 PM ---------- Previous post was at 09:18 PM ----------
P.S. yes I also tried to install from zip using the custom recovery, but it said it couldn't mount /sdcard0 or /system or anything when I tried. I think the best option is for me to find a method of removing my custom recovery?
Th elink to the KitKat 4.4.2 update.zip is here: http://we.tl/FGgNDO2ts2
It will only be available online until the 31st August, so if anyone wants to download it/play with it etc... then do so before then.
Thanks a bunch!
P.S. I've bricked my phone trying to mess around in CWM... hoping my nandroid backup restores properly!
James666PKR said:
Th elink to the KitKat 4.4.2 update.zip is here: http://we.tl/FGgNDO2ts2
It will only be available online until the 31st August, so if anyone wants to download it/play with it etc... then do so before then.
Thanks a bunch!
P.S. I've bricked my phone trying to mess around in CWM... hoping my nandroid backup restores properly!
Click to expand...
Click to collapse
so u finally bricked it just soft brick right ?
notice something strange it says it can't mount storage yet it backed up your rom it's probably just update script that needs tweaking
Possible Vanilla KITKAT rom
took rom from blu life 8 ported it it booted but got stuck on starting apps once boot.img seems to be giving the errors just have to pull boot from life 8
Pretty sure i've hard bricked it now
Tried to flash the update.zip using SP flashtool, but my phone wont even turn on/go to recovery now.. Computer detects it, but just a blank screen ... going to see if fastboot works, then try and manually install the boot.img etc...
---------- Post added at 01:32 AM ---------- Previous post was at 01:10 AM ----------
If anyone has any idea how I can unbrick my phone I would be all ears...
I have tried all combinations of buttons, but the screen just won't turn on. When I press power+volume up+volume down, the flash on the back, flashes once... but thats it... why is there no information about bricked vivo iv's or gionee elife s5.5's on the internet
James666PKR said:
Pretty sure i've hard bricked it now
Tried to flash the update.zip using SP flashtool, but my phone wont even turn on/go to recovery now.. Computer detects it, but just a blank screen ... going to see if fastboot works, then try and manually install the boot.img etc...
---------- Post added at 01:32 AM ---------- Previous post was at 01:10 AM ----------
If anyone has any idea how I can unbrick my phone I would be all ears...
I have tried all combinations of buttons, but the screen just won't turn on. When I press power+volume up+volume down, the flash on the back, flashes once... but thats it... why is there no information about bricked vivo iv's or gionee elife s5.5's on the internet
Click to expand...
Click to collapse
if the computer still detects it it can be saved so its not totally dead the update.zip wont install via sp tool there is a gionee firmware u can try but it might kill the phone with certain files will just have to uncheck them does sp tool detect ur phone? i backed up my 4.2.2 system.img i'll upload it and then u can try it on sp tool
taalibj01 said:
if the computer still detects it it can be saved so its not totally dead the update.zip wont install via sp tool there is a gionee firmware u can try but it might kill the phone with certain files will just have to uncheck them does sp tool detect ur phone? i backed up my 4.2.2 system.img i'll upload it and then u can try it on sp tool
Click to expand...
Click to collapse
I've tried responding to your PM, but my messages aren't being registered as sent!
If you did recieve them (2 now) awesome, if not, write me here and i'll respond.
I would love to use your 4.2.2 image if you ocudl upload it. I would be forever grateful!
4.2.2 system.img
well here it is https://www.dropbox.com/s/gd95xz06j2oy6pb/system.img?dl=0
you may need to rename it to android.img maybe but try system first
hey could u upload the drivers u used for ur phone i installed almost every driver known to man kind and mtk tools still doesn't recognize the device
taalibj01 said:
well here it is https://www.dropbox.com/s/gd95xz06j2oy6pb/system.img?dl=0
you may need to rename it to android.img maybe but try system first
hey could u upload the drivers u used for ur phone i installed almost every driver known to man kind and mtk tools still doesn't recognize the device
Click to expand...
Click to collapse
Just downloading now.
I was using the drivers that windows installs 'from the phone' when you plug it into windows. Those drivers worked fine... I then started messing around with downloaded drivers (probably all the same ones you have tried) and all of them just did the same thing or didn't work.
FYI, MTK Tools no longer detects my phone. It only detected it when it was booted (in CWM for me, I never tried it when it was actually working, in the OS). My phone only gets detected in 'device manager' and 'SP flashtool' sometimes.
I can upload all the drivers I tried downloading, but I think the more drivers you install, the more incompatibility there is... In the end I downloaded USBDeview and uninstalled all the 'phone' related drivers on my computer, then just used the drivers that automatically get installed when you plug your phone in.
I'm just researching how to flash this system.img file you have uploaded (thanks), using SP Tools. If you've done it before could you let me know how? I don't want to mess anything else up now.
Thanks.
I managed to install Gionee Elife s5.5 ROM using SP Flashtool easily, and my phone now works!! Well, sort of.
The screen keeps freezing, touch screen keeps now working (have to press sleep button, to refresh it).
I am hoping the OTA update will fix all these problems! Fingers crossed...
I really want to get the Blu Vivo iv firmware though, as there are loads of chinese characters on this phone, even with English language on.
If anyone could backup their phone using MTK tools, and upload the entire backup for me and everyone else that needs it, that would be great! Then anyone who bricks their phone could unbrick it by flashing the firmware useing SP Flashtool!
Thanks for eveyrone's help especially taalibj01!!!! You are a legend!
Don't know how it's possible but here it is Blu Firmware files!!!!!
James666PKR said:
I managed to install Gionee Elife s5.5 ROM using SP Flashtool easily, and my phone now works!! Well, sort of.
The screen keeps freezing, touch screen keeps now working (have to press sleep button, to refresh it).
I am hoping the OTA update will fix all these problems! Fingers crossed...
I really want to get the Blu Vivo iv firmware though, as there are loads of chinese characters on this phone, even with English language on.
If anyone could backup their phone using MTK tools, and upload the entire backup for me and everyone else that needs it, that would be great! Then anyone who bricks their phone could unbrick it by flashing the firmware useing SP Flashtool!
Thanks for eveyrone's help especially taalibj01!!!! You are a legend!
Click to expand...
Click to collapse
https://www.dropbox.com/s/qt0i6d2og8ge0sc/BLU_D970l_V11_GENERICK_T8493.zip?dl=0
I hereby nominate you for a knight-hood. I will contact the Queen and get her to knight you 'Sir Amazing'!!! I'm downloading now, will let you know how it goes and if it all works correctly!!!
Blu vivo iv drivers
these drivers are for gionee and Blu vivo iv just install its auto install so its easy
https://www.dropbox.com/s/x8umdofqgwbjbr1/GN_Driver_V1.3.0_Test.rar?dl=0
https://www.dropbox.com/s/yk08ekq3hf23zs0/MauiMETA_exe_3G_v6.1336.1.rar?dl=0
taalibj01 said:
https://www.dropbox.com/s/qt0i6d2og8ge0sc/BLU_D970l_V11_GENERICK_T8493.zip?dl=0
Click to expand...
Click to collapse
If you have bricked your Blu Vivo iv, or installed a custom recovery therefore could not upate OTA to KitKat 4.4.2, look here!
So everyone who needs to flash the new KitKat firmware from Blu follow these instructions!
Download the following file: https://www.dropbox.com/s/qt0i6d2og8ge0sc/BLU_D970l_V11_GENERICK_T8493.zip?dl=0
(Supplied by the amazing 'taalibj01')
If you have not previously installed the MTK drivers (usually installs from the phone when you plug it into the computer) please download and install from here:
https://www.dropbox.com/s/x8umdofqgw..._Test.rar?dl=0
https://www.dropbox.com/s/yk08ekq3hf...336.1.rar?dl=0
Also download/extract SP Flash tool from here (latest version): http://androidxda.com/smart-phone-flash-tool
Before you start, when you connect your 'powered off' phone via USB cable whilst holding the up button, your phone should be recognised in 'device manager' as 'MTK COM USB (COM4)' or something similar, under the 'Ports (COM & LPT)' section. If it is not, then you need to install the relevant drivers (above).
Now you are ready to get started.
Turn off your Vivo iv phone and disconnect it from USB.
Unzip the BLU_D970l_V11_GENERICK_T8493.zip file to any location.
Open SP Flash Tool, and click the 'scatter-loading' button.
Navigate to the unzipped BLU_D970l_V11_GENERICK_T8493 firmware folder.
Double click the MT6592_Android_scatter.txt file
SP Flash Tool will then list all of the files it has read form the scatter file and automatically 'tick/check' each of the 'preloader/MBR/EBR1/UBOOT/BOTIMG etc... files.
Most guides will tell you to press the select 'Download' from the drop down menu, but I kept getting an error message, but if you highlight 'Firmware Upgrade' from the drop down box, you should be fine.
Click the 'Download' green button.
Now plug your phone in whilst holding 'volume up' button.
SP Tools should recognise the phone, and the bar along the bottom should turn RED. The phone will disconnect, then recconnect again after a few seconds, and the bar will turn Yellow and it will say 'Formatting', then it will Flash the files to your phone which should take 30 seconds or so.
After it is done, a nice green circle saying DONE will pop up. You can now disconnect your phone, wait a few seconds, then power on using the power button.
All Done!!! KITKAT is now installed on your bricked phone!
Enjoy!
Hello, thanks for making this thread! Not much help out there for this phone. I started following your instructions, and immediately ran into a problem. On the step below...
taalibj01 said:
use mobile uncle from market and update recovery choose recovery.img first item at top of the list the downloaded recovery img must be in base of internal storage do not place in any folders!!!
Click to expand...
Click to collapse
...I opened the Mobile Uncle app on my phone, went to update recovery option, and chose the recovery.img from my SD card. The app popped up a message that read...
Mobile Uncle said:
Please Root your Android first!!
Click to expand...
Click to collapse
I just got the phone a few days ago, and it had KitKat 4.4.2 already installed from the factory. What do I need to do? Thanks!
Well I solved the problem. I downloaded Kingo Root and it successfully rooted my phone! I ran Mobile Uncle to verify, and it confirmed my root status.
My question now is, should I install the Carliv recovery, and flash bootimgADB.zip? Or, am I good to go now? I have SuperSU v2.02 installed. Thanks!
---------- Post added at 09:55 AM ---------- Previous post was at 09:09 AM ----------
So, I went ahead and tried to install the recovery.img using Mobile Uncle. It ran for a second, then a pop-up asked to reboot into recovery mode. I hit ok, but it rebooted into the orange and grey stock android system recovery.
So, I figured I would try to install the bootimgADB.zip from SD card, but it just comes back with installation aborted.
Any thoughts?
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
nexus_5_ said:
I have a nexus 5 16 GB and i downloaded the recent software update android 6.0.1 and then I decided to root and I used 'Nexus root toolkit v2.06' and first unlocked the bootloader and then rooted. Everything worked fine but after the process was complete it was rebooting and the booting animation went on and on for many hours and the device did not root. I really don't know what's going on. My purpose is to install a custom rom: cyanogenmod 12. Now what should I do ???? PLEASE HELP. When i try to enter recovery mode it shows a picture of the android mascot with opened back and exclamation and cannot enter command as well. and after some time the booting animation begins and goes on and on...
please help...
Click to expand...
Click to collapse
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Thank you very much for the reply, I really do have no idea as to how to flash the factory image because i am very new in this area. Could you please recommend software and which factory image i should download, please ?? thanks very much.
:good:
funnel71 said:
Unless something has changed, version 6. requires that you flash a special kernel before you can root your phone otherwise you are as you are now, stuck in a boot loop. You should probably download the factory image from Google, and then flash the system image to get rid of what you have done.. Perhaps then your phone will start normally
Click to expand...
Click to collapse
Also, you mentioned a 'special kernel' what does that mean. All i want to do to my device is install cyanogenmod 12 and for that i believe it needs to be rooted, so i am really confused. What should I do know
I'm having this same problem, and unfortunately, when I start the phone on fastboot, I can not access the recovery mode in order to upload a factory image of nexus 5.
I used the new tool available her for quick flash, and now, I don't have a phone.
First, don't panic. Your phone is still very easy to recover. Unfortunately I can't get you a complete walkthrough here (for now at least), so I'll give you the main idea and you'll have to do your homework (as maybe you should have done before).
1. You need to get fastboot working on your computer. It's included in the Android sdk package, but there might be some easier way to get it. Google it. You might need drivers for your pc too. Google it as well.
2. Then you need to get into fastboot mode on your phone. To do it, hold down power button AND volume down button until it gets into fastboot mode. You will see an android on his back with the cover open. At this point, connect your phone to your pc, open a terminal on your pc and type "fastboot devices" without the quotes "". It should find your phone if fastboot is working. If it doesn't work go back to step 1.
3. Download TWRP recovery on your pc and place the img file in the same folder as your fastboot executable (not mandatory but easier). It can be found here https://dl.twrp.me/hammerhead/
4. Always in fastboot mode, type "fastboot flash recovery twrp-2.8.7.1-hammerhead.img" assuming you downloaded that file, which you should have by the way. It should install fine. If you haven't placed the file in the same directory as your fastboot executable, you will need to provide the path to your img file as well.
5. Then use the volume rocker to switch between modes and choose reboot recovery.
6. You should now be in TWRP recovery. At this point, download a custom kernel (anyone found on xda for hammerhead should do) and push it to your phone. It should be fairly simple with TWRP. Then flash your new kernel using install. It should help you get your phone booting normally. Alternatively, you can download a custom ROM like cm12.1 and flash it altogether. It will install everything needed for your phone to boot up too. Beware if flashing a ROM though, I strongly advice you to do a factory reset before flashing it. You will find that option in the wipe menu.
Hope it helps, let me know if you need further assistance.
Yesterday, I have tried everything to have my computer to recognize the "fastboot" command, and I installed like 2 or 3 different programs for that. With my old Windows 7, I have been able to push a flashed image to fix this issue, using the fastboot command, but with Windows 10, it's always telling me it's not a valid command. I'll keep trying it, otherwise, i'll have to "resurrect" my old Windows XP computer.
Also, I noticed now that, while trying to install the fastboot, as per some files that I could download, but no file has been copied into my computer, not even if I run it as admin.
fixed. but no RECOVERY mode options....
Hi Guys,
Thank you very much for the help, I have finally recovered the phone and running android 6.0 MRA58N but it is not rooted. Now if you don't mind could you teach me how to root because i have checked lots of videos and tuts but none worked for me...
IMPORTANT:
when i am in recovery mode why cannot I access options even when i press volume up + power button and release them at the same time...????
Thanks in advance.
Just flash a custom recovery via fastboot. Just make sure your bootloader is unlocked. Can't link though.
hi guys i have used nexus 5 mobile with cyanogenmod 14.1 .It worked properly in 1 year. after that suddenly switched off and it not properly boot up .i try to switch on my mobile , first it show google with unlock logo properly and when it show cyanogenmod logo it stuck and again show google with unlock logo....i try recovery mode to wipe and flash the same rom ....the process is interrupt at middle stage and again show the google..i try lots of time . after few try that process finished completely without interrupt. then use my mobile 1 day same as i used first time root. after that same problem occur on my mobile ..so help me guys
@[email protected], possible power button problem?