Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
What is your recovery?
cortem said:
Right now my phone is stuck in recovery with no ROM installed, so I tried to adb sideload one.
Whenever I try to do anything with adb, my phone does not register at all with my computer under adb devices.
Is there any way someone could help?
Click to expand...
Click to collapse
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Danny Samuel said:
Make sure u have installed the drivers on ur PC.....
If u havent installed Try HTC Sync that will automatically install the necessary drivers...........
Gud luck
Click to expand...
Click to collapse
Also, let us know the OS you are using.. Win 8 x64 is a tricky BS.. sometimes the drivers work, some times they don't...
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
I'm on Windows 7 and had the same problem the other night when I needed to sideload a rom, it just would not find my device. Even though I had previously flashed kernels without any issues.
I ended up removing the drivers, re-installing them using Hassoons toolkit and rebooting both PC and phone. It will work, just can be a bit finnicky. I used his toolkit to sideload a rom through twrp.
cortem said:
for my recovery, I have TWRP 2.5.0.0
I'll check my drivers just in case.
For my computer OS, I have windows 7 x64
Click to expand...
Click to collapse
I hope you are giving enough time for the device to be recognized.
BTW TWRP has been updated to 2.6
Sent from my GT-I9300 using xda premium
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Thank you for the reply mate, sorry to hear you are in the same situation more or less.
Further reading over at Stack overflow help forums seems to lead me to believe the tablet is bricked. Loss of su/root privileges means no r/w access via adb to put the required files where they need to be, or install or TRWP.
I'm not giving up on this... well not yet. I have a ton of other work related things going on right now that I need to clear down so I can look into this a bit more seriously. I'm away till the 17th April but will check in here when I can. And, if I find a solution I will post it here.
smirnofred ;0)
smirnofred said:
Hi,
I have a UK Nabi2 which I used Nabilab2 to install TWRP+root+google apps a while back. I needed to do the new two part OTA update, for warranty reasons, so went to install my original backup, but could not find it. I used Nabilab2full and did the stock install, which removed root and returned the device back to stock. (This also changed my nabi to a US version with no serial, FW 2.1.29. which I later found out). & at that point I still had TWRP.
I did the first two of three OTA updates (which worked), the third update crashed during install. I retried the OTA twice more but each time it crashed. The device lost TWRP after this.
Upon entering recovery with ON/Vol+ I now get <3e> recovery. Running the root.zip file from sd card fails (I assume as I am not in the correct mode or have a bad file?). The OTA updates I grabbed from the nabi wiki page (and the thread, see below) also fail.
My device does not show in fastboot. Adb sees it but when using the command, C:\adb reboot recovery, the Nabi reboots and goes to the dead android (pushing -/+ to get into) <3e> recovery, and adb at that point no longer sees the device. The nabi also disconnects once adb shell is executed. I can intsall .apk files via adb command but I still need root access to run TWRP backup manager. I can run the root.zip file via an apk installer, but when running SU it gives a message 'There is no superuser binary installed, and superSU cannot install it. This is a problem!' ...Is there another way can I install root and/or the recovery.img to the Nabi2?
(I have been following the thread here, http://forum.xda-developers.com/showthread.php?t=2041224&page=10, as well as several hours worth of reading various adb, <3e> recovery, lost root etc q&a's in other places but cannot find an answer, or it's assumed that the adb reboot recovery command is working, which mine appears not to be).
Any help or pointers in the right direction would be very appreciated.
Regards,
Smirnofred
Click to expand...
Click to collapse
You need to select fastboot protocol in the menu after booting with pwr/vol buttons. Then install fastboot driver, then install TWRP. From that point the thread you linked will work.
scotia_rfc said:
Hi,
I have quite a similar issue with this. I flashed custom recovery and forced gapps, but now cannot flash original recovery to perform OTA update. Cannot boot into custom recovery at all.
Done a system restore so now i have lost the gapps that were pushed and cant get into recovery to flash them again :crying:
Click to expand...
Click to collapse
Doesn't matter if you flash the original recovery, you need to flash the original system. TWRP can do the OTA but it will fail because there are a couple of system files that were changed that fail SHA-1 checks. Don't know what version you are on or if it's a UK or US or Disney/Nick version.
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
smirnofred said:
aicjofs,
Thanks for the pointers! ...its most appreciated.
After checking, I do see the nabi in device manager when its in fastboot mode, but its not installed properly (it says 'Android device' but has a 'fastboot' icon with an exclamation mark under it) which would be the root of my issue I would have thought. I was certain the fastboot drivers were installed too, obviously I was wrong.
*EDIT*
Success!
I had java disabled. I also had issues with device manager switching from 'Android device' to 'Unknown device' intermittently.
I started fresh by uninstalling everything nabi/sdk/adb related. Re-installed java, sdk and adb drivers, in that order, which resulted in no conflicts or driver issues! Then when I put the nabi into 'fastboot protocol' the second menu then appeared (which it was not doing previously). I flashed the 2.3.3.0 TWRP recovery image.
Now I have some more reading to do about what image I need to put back onto the nabi.
Thank you.
*EDIT*
Thanks again.
Smirnofed.
Click to expand...
Click to collapse
Somewhere in that post you linked I put a pretty good procedure for getting a UK Nabi to the latest OS, hopefully you will be up and running in no time.
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
smirnofred said:
I'm there, finally. Using the link to the three part install you posted. http://forum.xda-developers.com/showthread.php?t=2041224&page=10 post #98
I'm now @ 2.2.2 (I think), 4.1jb, with 2.6.3.0 twrp recovery. First thing I did was make a full backup (once it was all working 100%).
I had a minor issue with SU trying to install repeatedly once I put the 2.2+ stock image (+modded ota), which sent the nabi back to <3e> recovery. But I just flashed it back to 2.6.3.0 with fastboot.
Many thanks ;0)
Click to expand...
Click to collapse
Hi Smirnofred, I have similiar issues to you, and i'm wondering of you can help. The 2.2 file from dropbox is no longer available, have you still got it? and would you kindly upload it somewhere for me if you have time. It would be much appreciated. :good:
James
I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
ceevaa said:
Hello everyone,
first of all im a total beginner on this field and it's the first time doing this stuff.
since there are no updates further than 4.2 for the beautiful HOX+ i tried to flash the cyanogenmod11 rom on my device. i used hasoons all-in-one toolkit. i followed the guide step by step and got stuck now in a hopefully not that serious problem.
i unlocked bootloader and flashed the cwm international recovery. the recovery was working fine and i did a backup. then i flashed the kernel with the boot.img from the cyanogenmod11.zip and the problems started. when normally booted the phone lights up with the white htc screen and then turns off again after about 3 seconds. i haven't flashed the CM11.zip yet and i guess that was the mistake? i still can acces the recover as well as the bootloader but like already said the phone doesn't start. another problem is that adb doesn't find the device enymore and only prints an empty line when using "adb devices" howevery using "fastboot devices" still gives me the proper result. hasoons toolkit also doesn't recognice the phone anymore.
if anyone could help either getting back to a custom rom or preferably setting up cyanogenmod properly would make me really happy =).
i hope this is the right place for this. i also searched around for hours and hours but can't find anything that helps me.
Lukas
Click to expand...
Click to collapse
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
leefear said:
so you have installed the kernel but not the rom? if so, then you need to flash the rom and then it should work
Click to expand...
Click to collapse
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
ceevaa said:
thanks for the answer so far.
the problem with this is that i cant flash the .zip using fastboot so i have to get an cyanogenmod image i think? dont know if that is somewhere out there ill check when im back home later.
Click to expand...
Click to collapse
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
leefear said:
you normally flash the zip via recovery, do you already have the zip on your phone?
if so, go into recovery and install, find the zip file and install it
if you don't have the zip on your phone then you will need to sideload the zip to your phone, (fancy way of copying the file to your phone) then post 4 tells you how to sideload the rom: http://forum.xda-developers.com/showthread.php?t=2066390
thanks
Click to expand...
Click to collapse
the problem with this is that i first don't have the zip on my phone so cant install from the recovery and second that adb doesnt recognize my phone for whatever reasone so i can't sideload the rom. if anyone experienced similar problems (fastboot working, adb not) please let me know how to fix it
Lukas
another thing i just read about is the possibility if one already has installed a running cyanogenmod rom on his device he can extract that as an system.img if i remember right and i could use it on my hox+. just in case anyone knows how to pull that off let me know =)
otherwise still looking for hints how to install rom via fastboot or how to make adb working again
Lukas
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
ceevaa said:
this phone is killing me -.-
now when entering fastboot mode it says battery too low to fast boot. so i connect it to the charger overnight but it apparently doesnt charge anymore.
help, please =(
Click to expand...
Click to collapse
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Moynia said:
Try flashing the ROM onto the phones storage. Then you can install the ROM. If you cant even charge your phone then you have bigger problems than not having an OS installed.
Click to expand...
Click to collapse
Hey thanks for the answer
but how do i flash the rom on the phone storage using fastboot?
Lukas