Database Users

Really stuck

Hey, ive recently updated the rom on my phone from cm 6.1 (stable) to cm7 nightly (vendor ace) -
initially i did it to test it and to see if it would fix my problem were the phone screen would automatically turn off when reciveing and sending calls, which resulted in taking out the battery and turning back on(which is now randomly working again)
after i flashed the cm7(via rom mamanger) it worked fine, got back onto the phone and i didnt have market and my phone wasnt connecting to google accounts aswell, so i then installed gapps. it worked the first time and it said it was succesful.
Restarted my phone and its the same, no market..etc..
so i tried it again, same thing, then for some reason when ever i try and load into the recovery from rom manager or from the inital vol - and power, it just freezes on the HTC startup screen.
The only thing i think i may have done different was adding this file to my phone (recovery-ace-3.0.0.5.img) because someone on cm7 told me i needed it, but i have no clue what it was for nor how to load or flash it.
So my main problem is, gapps wouldnt install and now ic ant access the recovery manager either and im getting kinda bored without my precious DHD
Can someone please help me

Just to make this clear, you cannot access your recovery even through bootloader? Can you get to the bootloader?

jkoljo said:
Just to make this clear, you cannot access your recovery even through bootloader? Can you get to the bootloader?
Click to expand...
Click to collapse
i cant access the recovery manager through the boot loader either but yes i can access the boot loader

Okay, then download this file:
http://dl.dropbox.com/u/18138289/reco.img
And then download radio flash.zip from radio.img flash guide sticky, extract it, open "start here", drop reco.img to the radio flash folder and type:
fastboot flash recovery reco.img
Click to expand...
Click to collapse
Your device has to be in bootloader>fastboot mode. After that you can access recovery, do a full wipe and flash CM6.

Ill try this now and reply once its done, erm why flash cm6? or do you think the same fault will happen if i try and reinstall cm7?
do i have to be in the bootloader from the beginning?
plus is there htc sync for MACs?
Thanks alot btw

Well, you can try to flash the cwm 3.img like I described and then install CM7, but I know for sure that the recovery I linked works with CM6.
You have to be in bootloader fastboot when you issue the command, yes.
I do not have a MAC, so I am not really sure. I think that you would have to get Android SDK and forget about radio flash toolkit if you want to use a MAC.

And then download radio flash.zip from radio.img flash guide sticky, extract it, open "start here", drop reco.img to the radio flash folder and type:
right so whilst i do all of this, i need to be in the bootloader > fast boot - sorry just want to clarify, ive not done this before but i have faith!!

Yeah, it does not really matter, but I would put my phone to bootloader fastboot so it is ready. The important thing is that your device is in fastboot mode when you enter the fastboot flash command.

Kool Kool, well thanks alot im going to try this now

right so i successfully entered the recovery, thanks alot for the help with that.
I tried to reinstall cm7 -worked and gapps - said it worked, but it still wont bring up the market app, why is this?
i reinstalled a back up and everything is working again, im so confused why it wont bring up the market app in cm7

o0jaz0o said:
right so i successfully entered the recovery, thanks alot for the help with that.
I tried to reinstall cm7 -worked and gapps - said it worked, but it still wont bring up the market app, why is this?
i reinstalled a back up and everything is working again, im so confused why it wont bring up the market app in cm7
Click to expand...
Click to collapse
when you boot into recovery, not just through rom manager, does it say you have cwm 3.x installed? if so try re-flashing the gapps, if not go back into fastboot and flash cwm3.

Wow, really sorry about that, i thought the cwm was a custom firmware i thought t was optional, sorry for the inconvenience, but thank you alot this has been daunting :/
flashed the right recovery, and everything is working as it should be, thankyou both very much

[Q] Can't use recovery, but fastboot works fine

On my phone, can not boot into recovery mode. No matter how many times I try to use the home and power button. I even went to youtube to watch a video on it to make sure I was doing it right.
I have installed clockwork recovery via fastboot many many times, using different versions. I also have tried it with different roms installed.
I wonder if it is because the first rom I installed was superfast froyo, which says recovery is not working. I also installed swiftdroid 2.0, which also wouldn't let me use recovery. Though I forgot to try to reboot into recovery from the android menu when I had swiftdroid installed.
It's not a big deal anymore, since I accomplished what I wanted. I installed Froyo Optimum V3 with data2system via fastboot, and it worked fine. I now have 245mb on the phone so it is all good. When I installed it I just installed boot.img, cache.img, and system.img each to their respective partition, and data.img to userdata partition. So far, everything works fine.
However, it does bother me a little that recovery isn't currently working, I'm sure I'll find the answer sooner or later. Anyone have any ideas?

Hello as I can see you recently uppdated from stock 2.1? Then something went wrong and you used a rom that does not support recovery. Please tell what .kdz you flashed
EDIT: http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26

lavero.burgos said:
Hello as I can see you recently uppdated from stock 2.1? Then something went wrong and you used a rom that does not support recovery. Please tell what .kdz you flashed
EDIT: http://forum.xda-developers.com/showpost.php?p=13205397&postcount=26
Click to expand...
Click to collapse
All Fastboot ROMs support recovery regardless of their version.
Try this:
Go into fastboot and open a Command Prompt and type:
Code:
cd <location of SDK Tools>
fastboot erase recovery
fastboot flash recovery nameofrecoveryimage.img
fastboot reboot
This fixed my problem I had when I first flashed fastboot onto my GT540, don't know if it will work for you or not, but its worth a try
Hope it helps,
Jack

Original poster here. Changed name for obvious reasons.
I think something did go wrong during the initial upgrade to 2.1. I forgot to mention a couple of things now that I think about it.
I used this link for most of my information:
http://forum.xda-developers.com/showthread.php?t=1032744
I first installed the european rom listed in that thread via KDZ. I never get an LG screen during boot up. I don't remember if the stock 1.6 had an LG screen or not. I think upgraded to what was then called "super fast froyo 2.2." I then wanted to install a rom with data2system, when was when I realized restore wasn't working. I then tried to downgrade back to the european rom via KDZ. It didn't work. Whenever I booted the phone, all I got was a black screen similar to the fast boot screen. I re-installed the european rom via KDZ, same results. Installed "swift droid 2.0" via fast boot, no recover. Then I installed I installed Froyo Optimum V3 with data2system, via fastboot, which is where I am now, still with no lg screen during boot-up.
Thanks you for your help, and i will try the link posted by JackG256 when I have time.

typci said:
Original poster here. Changed name for obvious reasons.
I think something did go wrong during the initial upgrade to 2.1. I forgot to mention a couple of things now that I think about it.
I used this link for most of my information:
http://forum.xda-developers.com/showthread.php?t=1032744
I first installed the european rom listed in that thread via KDZ. I never get an LG screen during boot up. I don't remember if the stock 1.6 had an LG screen or not. I think upgraded to what was then called "super fast froyo 2.2." I then wanted to install a rom with data2system, when was when I realized data to system wasn't working. I then tried to downgrade back to the european rom via KDZ. It didn't work. Whenever I booted the phone, all I got was a black screen similar to the fast boot screen. I re-installed the european rom via KDZ, same results. Installed "swift droid 2.0" via fast boot, no recover. Then I installed I installed Froyo Optimum V3 with data2system, via fastboot, which is where I am now, still with no lg screen during boot-up.
Thanks you for your help, and i will try the link posted by JackG256 when I have time.
Click to expand...
Click to collapse
Actually the link you see was the one posted by me lol i recently posted on my reference guide thread aboutcases when you brick your phone and possible fixes, there is one for your problem.
Also as i have read plenty about this kind of things i can assure that not all the kdz with fastboot support recovery that is a myth , there is a recovery_rom.kdz, there is out.kdz and other .kdz roms that has a purpose.
My theory is that not all the LG GT540 are the same thing, why? because simple if you read all the threads of users that have had issues with their phone saying this ROM worked for me and then another user saying that it didnt for him but other rom did the job. There are so many .kdz ROMS and even more are been released, but modified to support fastboot and recovery.
So if you do a bit more of research you can find original stock .kdz roms and their modified version requested by many users marginalized because of their location.
Hope you fix yor phone with the one posted in my thread, good luck! you will need it.

I think you are correct about not all gt540 are the same. I have an "international version." When I was installing drivers, it was a very complicated issue, and most of the drivers I found didn't work. I had to use the drivers supplied by LG via their lgmobile update program, to get my phone interact correctly with my computer. Luckily, I have alot of experience with flashing and custom roms for other electronic devices. So I know how to handle bad flashes, and other problems for the most part. Right now, my gt540 is fine, no recovery, but the custom rom is working just fine. Next time I want to swap out custom roms, probably when the android 3.3 builds become very stable, I'll play around with some KDZs and try to get recovery working.
Thanks for your help.

If you want to try with more kdz then you should try with one modified by mur4ik for data2system method.
Sent from my GT540 using XDA App

can someone please help?

I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!

You can use fastboot to erase your current partitions then manually flash the 4.3 stock images.

I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.

chrisbo4 said:
I've never used fastboot before. Plus another problem now... I tried to flash the stock image via toolkit, now the device is stuck on the bootloader.
Click to expand...
Click to collapse
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.

Rirere said:
On the bootloader or the boot animation? Big difference.
There was a recent change in fastboot that makes flashing the 4.3 images a little dicey if you're not using the latest fastboot executable, which I imagine could cause problems with various toolkits that bundle the executable.
Click to expand...
Click to collapse
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.

chrisbo4 said:
On the bootloader. I can't get past the google splash screen, but it overlays the bootloader screen. I just want to get back to stock, then upgrade to 4.3. I've tried to install adb on my computer, but couldn't get the computer to recognize the device.
Click to expand...
Click to collapse
Install this through device manager.
http://d-h.st/kDu

Username invalid said:
Install this through device manager.
http://d-h.st/kDu
Click to expand...
Click to collapse
Okay, it's installed. I'm not sure what I should unzip though?

chrisbo4 said:
Okay, it's installed. I'm not sure what I should unzip though?
Click to expand...
Click to collapse
You can either flash stock images with fastboot or install TWRP then flash stock zip file.

chrisbo4 said:
I'm trying to update my wife's N7 to 4.3. She used a toolkit to root and has TWRP recovery. Everything else is stock. So first I downloaded the 4.3 update and attempted to flash, but immediately after choosing "install" I received a message the the flash failed. I thought maybe I got a bad download, so I rebooted the device and forced an OTA. The device downloaded the OTA, but then rebooted to TWRP and didn't install. Then I thought maybe I need to have stock recovery... So I unrooted, and installed stock recovery. I then forced the OTA again, downloaded, and began to install in stock recovery, and approximately halfway through it stopped and gave an error message. Then the device rebooted on it's own. I'm not sure what to do at this point. I was able to update to 4.3 on my N4 without any issues. Does anyone have a solution for me? Please let me know if there is some detail I left out. Thanks!
Click to expand...
Click to collapse
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!

gunner1937 said:
First of all I do not intend to offend you. I am not lecturing. I just want to give you my opinion in order to try to help you.
In general to install an update the safest way is to have or re-install stock recovery prior to the installation of the update. There is no need to unroot for the stock recovery installation.
In your household you have Nexus products. It means that you will probably continue to acquire Nexus equipment. In this case, in the long run, you will be better off installing, learning, and using adb and fastboot methods. Toolkits are mostly a quick fix which works ...............or not. I am thinking that toolkits are useless in the sense that they do not bring knowledge and experience (in my area trash collection are Monday and Thursday:laugh.
The XDA forum is full of resources. It does not leave a stone unturned. Its a matter of reading, asking, and learning.
In your case, facing your problem, I would install adb through a program called "android-sdk- windows". Then I will take advantage of the experience and the knowledge of our forum members to install the JB 4.3 factory image.
here are two references among several:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?t=1781250
But it is a long way for a beginner - which I was 2-3 years ago - to go this route. But what a reward!
Click to expand...
Click to collapse
Thank you for the information, and I'm not offended at all. I spent most of last night reading, and attempting to get adb running on my computer. I experienced issues getting drivers installed, and the computer recognizing the device. Also, trying to find the directories... I'll keep searching to see if I can get this figured out. Thank you again!

Thanks to everyone for helping me through this problem. After a lot of searching, research, reading, and video tutorials, I flashed stock images to the N7 via fastboot. I always thought that adb and fastboot was way too advanced for me (and it probably still is), but at least I got the basics down. Thank you all again.

[Q] Tmobile D801 will not boot FIXED

Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now

zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!

mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476

[Q] Phone has no recovery and other issues.

First want to say hi and that this site is full of knowledge so any help with my subject will be great.
Got a att s4 sgh-i337 phone. I rooted it before the lollipop ota update was out and everything went fine. Then the lollipop update came out and I followed one of the methods on keeping root and updating to 5.0.1 lollipop on the phone. Everything went fine with that. Still showed root status and never did the phone brick or have any issues in the updating.
At some point though, I did run triangle away because I would have the custom logo and opened padlock when the phone would boot up. I knew it wasn't a huge deal but the counter showed correct and never could just figure out how to get it to go away. Either way, I did run it and I think rebooting twice, the factory loading image came back to it. Now it shows my current status as 0 for the counter and the binary is Official.
I have not tried to load any roms or nothing like this to the phone, just followed the instructions to give it root access so I could run a few different apps and adaway for when I listen to Spotify.
One day, I was trying to install a new version of Words with Friends and it failed because I think wwf was open, but I did go back and install it. For some reason now, my phone never notifies my with a wwf notification when somebody plays me. Every now and then, it might pop up when I restart the phone but that is it. I don't think facebook notifies me everytime also but was more worried about words with friends.
Searching google, it says to go into recovery mode and flash the cache of the phone there. I have done the cache memory in the phone but that has not fixed my problem. When trying to go to recovery, it never works, it would always show, recovery booting and then load the phone up as normal.
I have download quick boot and rom manager since they all have an option to boot into recovery rather than pressing the buttons but it always does the same thing. Reading the web though, it seemed like I needed to install a different recovery than the factory I guess, so using rom manager, I tried twrp and that didn't work so I installed ClockworldMod 6.0.4.7. Rom manager shows that as the current recovery method.
When I try to boot into recovery, it still shows that recovery is booting and then goes straight to loading the phone as it should normally.
Now though, every time I restart my phone, it says recovery is trying to boot but never does.
How do I fix my phone to be able to boot into recovery and it not try to boot every time it powers on. I have tried searching google but I just just can find an answer to my direct problem. I know how to hold the buttons and go to recovery but does not work, and I also know how to get to it from the different app programs(rom manager and quick boot) but they do not work either. It would be nice to get the wwf notifications to work properly again also.
If you need any information from my phone, please ask. Thanks for any help on my matter,
Charlie

Odin stock and start over.

Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.

creepyncrawly said:
Apparently, you are not aware that the boot loader is locked, preventing the installation of a custom kernel. You can not use twrp, or rom manager. Rom manager itself may cause issues.
I agree you should flash back to stock and start over to get a clean install. Hopefully, this will solve the issues with notifications as well. You can use the "[GUIDE]Odin to Stock, Updating, Rooting, and Installing Safestrap" by guut13 in the general forum for files and instructions.
Click to expand...
Click to collapse
Thanks for the replies guys, I really don't know a whole lot about rooting other than following instructions about it. I was unaware you could not use the twrp or cwr as a recovery. My recovery did not work before so that is why I was trying to install those. I knew you could not install custom roms but I did not know that you could not use rom manager to install custom recoveries.
I appreciate the help so far and I will look into that thread you mentioned. I haven't read it but will this take me back to stock lollipop 5.0.1 and I just reinstall apps or will I have to re-root the phone.
Charlie

please delete, sorry
Charlie

You have to go back to 4.4.4, to the nb1 base, root with towelroot, and then use the keeproot method to get back to 5.0.1 rooted. The instructions are in the guide, and also a link to the keeproot thread is there.
By the way, for future reference, questions, help and troubleshooting issues should go in the Q&A forum, not the general forum.

not having any luck
Ok guys,
I am trying to follow the guide but not having much luck.
I downloaded the I337UCUFNB1_4.4_Stock_Odin_tar and put it in the AP Odin file. I'm not sure if I should be using it or the other file named I337UCUFNB1_4.4_Rootable_Stock_Odin_tar to begin with. The instructions said to use the first one so that is the one I was trying to use.
After putting the first file in the AP slot of Odin and hitting start, it begins to try to do it's thing and then says it fails!
What do I do now? Am I doing something wrong or what because I'm trying to follow instructions but not having much luck.
Please help. Sorry for posting in the wrong area also in the beginning.
Charlie

I'm screwed
Now when I turn my phone on, it says Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again?

doing better now
Pretty sure I got it going finally. I changed cords and then changed ports on my computer and it finally did go back to stock without an error. I'm currently back on Lollipop and rooted so now is the fun of reinstalling contact info and anything else. So far I have not rebooted but it was not showing the recovery booting option when it did reboot. Hoping my notifications work properly now also!
Thanks!!!
Charlie