Related
I pulled a boneheaded move and ended up formatting my phone from within the TWRP menu. Now the stock operating system is gone.
I wanted to put on one of the Gummy Nightly builds, but I'm new to TWRP and selected the wrong options while wiping.
So now I have the Gummy ROM on my PC, the phone is connected to my PC and in TWRP (in the advanced adb sideload feature), but adb will not recognize my phone.
When I check device manager, SAMSUNG_Android_SCH-I535 is there, but with a yellow "cauton" symbol. When I look at properties, it tells me that "The drivers for this device are not installed (Code 28).
I went out to the Samsung page and got the exe to unpack drivers on my machine... I've tried "update driver" and pointing to the root of the directory containing the Samsung drivers, but my PC claims none of them are applicable.
So what I'm looking for here is:
(1) How do I get this ROM on my phone so that I can install the zip and have a working OS again?
(2) Assuming that using the ADB Sideload feature of TWRP is my best option, how do I get the device drivers for my galaxy s3 installed to my windows 8 PC and get adb to detect it?
Thanks in advance.
Ok, so it seems to have gotten worse.
I cannot get my windows installation to recognize the phone without it being able to boot an android OS, it seems.
I had it in TWRP 2.6.0.0, but as I was trying to reboot to see if I could get into download mode (my thought being to change out TWRP for Clockwork; I seem to remember Clockwork Recovery having a "mount as USB" option which TWRP seems to lack), it tried to root the file system.
After that, the screen went black and nothing happened... the phone was unresponsive. I would remove the battery and replace it to have it vibrate once and then not respond to any key presses.
I removed the battery, SD card, and SIM card, replacing only the battery and got it to turn on and show a Samsung Galaxy SIII logo... but it's just sitting there... I'm assuming it's frozen because there's no OS to boot on the internal storage.
Please help me recover my phone!
Ok, so I've found I can still get into download mode, but not into recovery.
Recovery seems to lead to a black screen with nothing on it.
Trying to boot normally leads to the statis Samsung Galaxy SIII logo.
Can I fix my phone from the download menu?
Please help me.
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
ThePagel said:
Install kies and at the end of the install make sure you check install unified drivers. Then flash root66 through Odin. After that you should be good to install ROMs again.
Click to expand...
Click to collapse
Thanks for the reply!
Sorry, I'm a little out of date on the flashing and stuff -- I was just over in the thread where the poster thought he half softbricked his phone and was asking about 4.1.2 vs. 4.3
I see this at the top of my screen sitting here in download mode:
ODIN MODE
PRODUCT NAME: SCH-I535
CUSTOM BINARY DOWNLOAD: YES (6 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: ENABLE
It seems my bootloader got relocked somehow -- is this why my phone just goes to black screen when I attempt to boot into recovery -- even if I have TWRP or CWR installed? Odin claims I just pushed philz custom CWR to my PDA section, but it still won't go into recovery.
What are my options here?
You are pre 4.3 I'll help you more in the morning if no one else does first.
ThePagel said:
You are pre 4.3 I'll help you more in the morning if no one else does first.
Click to expand...
Click to collapse
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
corrosivefrost said:
Ok, thanks -- I appreciate that someone's willing to help! Googling stuff is just getting me more and more confused.
I'll stay tuned for help and turn off my phone so I don't screw things up further in the meantime.
My desired result here, I think is to have my bootloader remain unlocked (as I was under the impression it was, since I was running TWRP with rooted stock ROM), with CWR as the custom recovery software and Gummy as my current ROM.
Side note: I've noticed I don't even get a battery indicator on the main screen now when I press the home button -- is this because of whatever's causing my recovery to not work (and the potential lack of an OS)?
Thanks in advance.
Click to expand...
Click to collapse
Once you in download mode, can your Odin see your phone?
buhohitr said:
Once you in download mode, can your Odin see your phone?
Click to expand...
Click to collapse
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
corrosivefrost said:
I believe it can. After TWRP stopped working, I tried to replace it with CWR and the digital flash count went up (Odin showed no errors on the flash) -- recovery still won't work though, holding vol+/home/power simply gives me a black screen after I see the SAMSUNG logo with the recovery boot text in the upper left.
Click to expand...
Click to collapse
What stock version do you have on your phone right now?
buhohitr said:
What stock version do you have on your phone right now?
Click to expand...
Click to collapse
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
I'm really not sure what kind of state anything is in at this point -- other than Odin seemingly working and being able to get into download mode.
Again, short version of what happened:
(1) Accidentally did a full wipe (factory reset?) in TWRP -- this wiped the ROM I was going to install with TWRP off the phone.
(2) While trying to ADB sideload from TWRP and telling TWRP to reboot, TWRP tried to install supersu.
(3) After (2), I was unable to get back into recovery mode. I got into Odin and tried to flash philz customer clockwork recovery and it seemed successful. Reboot and attempt to enter recovery still fails. Samsung logo with recovery mode text appears, but then the screen goes black.
(4) Normal boot leaves the screen stuck on the Samsung Galaxy SIII logo indefinitely.
corrosivefrost said:
None? :silly:
I think before this fiasco, it was running whatever version was previous to the new VZW update.
It was the fact that the new update was trying to install and failing repeatedly (because my bootloader was unlocked, I think?) that prompted me to look into finally switching to a ROM. However, my unfamiliarity with TWRP led to me formatting my phone (everything, it seems, including the SD card)... so I'm not really sure what' "on the phone right now". :\
Click to expand...
Click to collapse
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
buhohitr said:
OK, download this image and flash with Odin(you should be using Odin version 3.07) http://goo.im/devs/invisiblek/i535/stock.vzw_root66.tar This should bring your phone back from the dead.
Edit: after you have your phone up and running, download goo manager and install cwm recovery since your phone is pre rooted already.
Click to expand...
Click to collapse
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
corrosivefrost said:
Ok, that looks like some version of the stock vzw ROM with root already installed?
This is what ThePagel seemed to recommend as well before I ended up with more questions about what was going on before I did it.
What part of Odin do I flash to? PDA again, just like a custom recovery?
Click to expand...
Click to collapse
Yes, it's pre rooted stock image and yes flash with PDA.
buhohitr said:
Yes, it's pre rooted stock image and yes flash with PDA.
Click to expand...
Click to collapse
Standard auto-reboot and f_reset_time options? nothing else necessary?
corrosivefrost said:
Standard auto-reboot and f_reset_time options? nothing else necessary?
Click to expand...
Click to collapse
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
buhohitr said:
Correct. When you click on PDA and select the image, give it time to showup in Odin cause the size is big.
Click to expand...
Click to collapse
Alright, I'll give it a shot and report back.
Thank you!
corrosivefrost said:
Alright, I'll give it a shot and report back.
Thank you!
Click to expand...
Click to collapse
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
ThePagel said:
If that doesn't work you'll need to flash the bootchain first. I don't have a link but I could find it if you need to use it.
Click to expand...
Click to collapse
It did work! Hooray!
buhohitr said:
Yes if the bootloader is still locked he needs boot chain can be found here http://forum.xda-developers.com/showthread.php?t=2046439
Click to expand...
Click to collapse
Didn't need to go that far -- but now that I'm back up and running, signed into google play, and downloaded goo manager, can you point me in the right direction for getting it to install cwm recovery?
Thanks guys!
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
agk.ganesh said:
Hi,
I have put more than 12 hours of my time, before creating this thread. I have tried things, but still struck, so thought to post it in a new thread. Thanks for all your time.
Currently struck in,
fastboot mode started udc_start()
I tried, fastboot erase recovery -> fastboot flash recovery recovery.img -> fastboot reboot (successfully). But it still struck at same place after reboot.
I tried with different recovery images, but still the same observation. I tried to boot by key combination (volume down+home+power), still same observation.
Earlier, I installed ROM manager through google play and installed CWM recovery, version 5.xxx (which I feel now is a mistake), as I tried to install CM11 from MukilSoni, which needs CWM version 6.xx +. I am able to go into recovery and select CM11 image through CWM and proceed with install steps. But, after initial selection in CWM (like app install, etc) it rebooted and went into fastboot mode.I checked the log, it ended with some return error 7.
Then, I tried to Google and check how to recover from fastboot mode, but all failed. I didnt tried KDZ method, but thought to hear from you guys before making it more messy.
Glad, if I get any help and appreciate it.
Thanks for reading it and your time.
Regards,
Ganesh
Click to expand...
Click to collapse
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
xu3sno said:
Did you ever try pull out the battery, reinsert, reboot system with 3 buttons combination? I got several fastboot mode as you're facing, and the system works just fine using above method.
I think you got just soft brick. Please, keep the device stay untouched until someone with such expertise to solve the problem will guide you. I think @akiratoriyama can share his bad experience bricking his lovely p500.
Wish you luck.
PS.
You must to press three buttons a bit longer, do not release it, until recovery mode appearing. Otherwise fastboot mode or blank screen showing instead.
Sent from my Optimus One using xda app-developers app
Click to expand...
Click to collapse
androidck said:
Two years ago I bricked my phone also after using ROM manger. Though I will never ever use this or similar tools again. But at least, if I remember correctly, I could revive my phone with the "fastboot erase recovery" method http://forum.xda-developers.com/showthread.php?t=1088046. But since you failed is seems to be another problem. I am not a fastboot expert , but since you bricked your phone with ROM manager too, I wanted to share my success story with above mentioned method and installing AmonRa recovery. So maybe you will give it a second try? All I can remember is, that it is extremely important to follow the instructions exactly.
Click to expand...
Click to collapse
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
agk.ganesh said:
Thanks @xu3sno & @androidck
I am also getting help from mukulsoni & others in Official CM11 version 10 thread.
I am able to go into the flash tool (pointed by mukulsoni, http://forum.xda-developers.com/showpost.php?p=49567169&postcount=45)
and able to go 'Select kernel to hotboot' with recovery.img (CWMod-6.4.0.6-Jan16)
But rebooting by HOME+Volume DOWN+POWER --> goes into CWM recovery of v5.0.2.0 (which i installed initially)
I am thinking, what to do next.
I will keep my progress posted here.
Thanks for listening..
Click to expand...
Click to collapse
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
ibub said:
Are you sure that you are booting into cwm v5.0.2.0?
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Click to expand...
Click to collapse
+1
CM10.1.6 worked
ibub said:
Are you sure that you are booting into cwm v5.0.2.0? Version is listed at the top. If that is true, then either the flash tool failed to flash cwm v6.4.0.6, or you have chosen the wrong recovery.img. This can easily happen since they all have the same name. Try to flash it again, but make sure that you use the correct image.
Also, I believe that you may not have any rom installed, or existing rom might be corrupted. So you may want to flash a cm-9 or cm-10.x rom first, just to stabilize and to be sure that you are healthy. Those can be flashed using cwm 5.0.2.0. I can post a link or two, if you'd like.
Edit: Here is a link to cm-10.1.6:
http://jenkins.androidarmv6.org/view/All/job/android/597/
Gapps already included.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
mns123 said:
+1
Click to expand...
Click to collapse
Thanks.
agk.ganesh said:
Thanks @ibub for your helping hand.
I will check why recovery image not upgrading as expected. (I didn't manually download CWM5.xx version to my PC. I got it via ROM manager app, so i hope I haven't chosen wrong image)
Yes, I got CM10.1.6 from your link and installation went successfully and able to boot up..
But, it is very slow. (May be it will take some time?!) I will check it.
Between, @mukulsoni advised to install CWM6.xxx via CWM5.0.2.0. I will check how it goes.
Thanks.
Click to expand...
Click to collapse
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Thanks
ibub said:
Yeah, I chose to post that link only to make sure that your phone is healthy. Now you can install any recovery/rom that you want. If your volume keys are broken, I suggest that you flash to twrp recovery. It's touch driven.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I will try installing now new recovery and then new ROM.
Very glad to see the support from you guys... Thanks ibub and all..
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Thanks
akiratoriyama said:
[rant] NEVER EVER USE KDZ. PERIOD. :crying: [/rant]
Best of luck on your ROM journey :good:
Click to expand...
Click to collapse
Thanks @akiratoriyama.
I have upgraded CWM recovery 6.xx through CWM 5.0.2.0 and successfully installed MukulSoni's Kitkat ROM.
And enjoying eating kitkat..
Thanks all..
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?
Hi hope this makes sense to you. X1032 Rooted on 4.4.4 with stock rom. Downloaded update for lollipop however once installing it goes to about 30% in and errors. Phone then boots back into normal phone 4.4.4 saying unsuccessful. Then five times my phone randomly restarts itself into the custom recovery and tries to install the stock update and gives the message shown in the attachments photo. Any reason for this?
Thanks
Try updating with stock recovery and without root. It should work with an unlocked bootloader too.
Thanks for your reply, as this is my first time reverting back to stock recovery and also how to un root the phone what is the best guide for me to follow as i dont want to mess it up. As i do it once ill always remember for future issues. You can probs tell the version of custom recovery via the screenshots.
Many Thanks
To get back to stock, download your phone's stock ROM, extract the recovery.img file and flash it using the fastboot commands "fastboot flash recovery recovery.img" without quotes.
There should be an option in the root app to remove itself and unroot the phone.
Thanks alot will do that and let you know how it went weather it works or not.
Thanks again
If you want to maximize the chance that you'll get the OTA update installed, flash all partitions in fastboot. Note that motoboot file may not flash if your phone has a newer bootloader installed.
Hi did what you said on previous post and still errors and boots back to normal phone. Custom recovery removed and unrooted. Unrooted using the supersu app and did full unroot, as for going back to stock recovery couldn't find a stock recovery for this build phone so used the new mototool v3.1 program to flash stock recovery back to kitkat.
Any suggestions?
What is your phone model? Carrier?
Xt1032 and 02 pay as you go
Try and find you ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1 There are a few pages of ROMs for the Moto G.
audit13 said:
Try and find you ROM here: http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=filename&order=ASC&show=100&page=1 There are a few pages of ROMs for the Moto G.
Click to expand...
Click to collapse
Thanks for your input and support, looked at that link and couldnt find the file i need. This screenshot in attatchments is the phone currently. Based on the screenshot is the file on this link below the stock rom? (its post #348)
Thanks also how would i flash this rom onto the phone and re write the firmware?
Thanks
Actually that link isnt working which of these two should i download?
Title: Android 4.4.4 - Blur_Version.210.12.40.falcon_utms.Retail.en.GB (Retail UK) (XT1032)
Filename: XT1032_RETAIL-GB_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip
Title: Android 4.4.4 - Blur_Version.210.12.40.falcon_utms.O2SL.en.GB (O2 UK) (XT1032)
Filename: XT1032_O2SL-GB_4.4.4_KXB21.14-L1.40_37_cid7_CFC_1FF.xml.zip
NOTE: the o2 sim card is pay as you go and the phone was origionally on EE as a one month rolling service but with it been unlocked when i passed the phone over to my mam to use she was able to put here o2 pay as you go sim in and carry on using the phone on her origional sim.
Thanks
It looks to me like either ROM would work as they are both for the xt1032 but I can't say for sure as I have no experience with f;ashing either ROM.
Im guessing that if i download the generic rom and their should be a guide on here for flashing it? Am iable to take a backup of the current rom installed incase things mess up?
You could use ADB commands to create a backup but it's not that easy to do in my opinion without a custom recovery.
http://www.howtogeek.com/125375/how...kup-without-rooting-or-unlocking-your-device/
http://forum.xda-developers.com/showthread.php?t=2542219
Will create a new thread asking for the easiest way to reinstall a stock rom. Thanks for all your help you have been great!
major problems!!!!!
Stock recovery installed to phone. Started update it was installing and got to 3/4 of the way through, errored, restarted and not goes in a loop saying no command!
Phone will not switch on!!!
Why has this happened?
morgiee said:
major problems!!!!!
Stock recovery installed to phone. Started update it was installing and got to 3/4 of the way through, errored, restarted and not goes in a loop saying no command!
Phone will not switch on!!!
Why has this happened?
Click to expand...
Click to collapse
It doesn't power on or it goes to a loop saying no command?
Try the following:
1. Plug it into the charger
2. Hold the VOL DOWN key
3. While still holding the VOL DOWN key, press and hold the POWER key
4. Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
5. After holding the keys down for more than two minutes, release them.
6. The Flash Boot screen will display, and the Normal Reboot option will be highlighted
7. Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
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?