Related
I bought a galaxy note today used and the guy said the home button didnt work because of a software update. i did some quick research and took the bait. Unfortunately I have discovered it is a hardware related issue. I wanted to try one last thing by flashing a new rom over to it.
The bad part is I rushed and flashed a gb kernel ( abyssnote) and It wont boot. I cant get into recovery because the home button is broken.
Does anyone know of any other way to get into recovery? when i plug it in my computer doesn't recognize it so adb/odin are out.
Im trying to get my money back but i need to unbrick this phone
Can anyone help? any solutions?
Fixed. Please delete
took the entire phone apart and finagled the button into working 1 last time
Just for next time if you can get to the boot animation usually you can use adb and type adb reboot recovery.
I tried many times. Unfortunately i had no luck.
Horrible first day with the note but it's not going to put a sour taste in my mouth!
nekoti said:
Just for next time if you can get to the boot animation usually you can use adb and type adb reboot recovery.
Click to expand...
Click to collapse
Sent from my GT-N7000 using Tapatalk 2
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
Are you running stock, or did you root and customize?
Try plugging it in to a computer. A lot of us are finding better results when you do. You may end up having to do more. But just being connected to a computer has helped in the past. Quick fix before you start trying adb
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
kiewee3 said:
Turn fastboot off in the power settings. I'm not sure if it has the fastboot setting, but that would be your problem.
Click to expand...
Click to collapse
Err ..... it won't boot.
Does ADB work at this stage? Assuming you are rooted with CWM recovery, try
Code:
adb reboot recovery
Then from recovery, power it off completely. If fastboot is the problem, this should workaround it for you.
morell2 said:
I have rebooted the tablet 10+ times with vol + and vol - and it is still stuck on the Google screen when it starts up. In fact I can't make it turn off, only reboot and go right back to the Google text screen. Any ideas?
Click to expand...
Click to collapse
It's karma because of your ridiculous signature.
Anywho. What did you do to the device? Attempt to root it? What happened between it working and not working?
khaytsus said:
It's karma because of your ridiculous signature.
Click to expand...
Click to collapse
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
Right. I can't figure out why people think others want to see large pictures of their crap.
just lou said:
Right. I can't figure out why people think others want to see large pictures of their crap.
Click to expand...
Click to collapse
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Rock-&-Roll-Hedgehog said:
Don't be mean. It's a visual aid to go with his query. Just in case we don't know what a Nexus 7 is (here in the Nexus 7 forum).
Click to expand...
Click to collapse
Oh. Now I see.
The nice thing is that Signatures can be disabled if you so choose, it'd just be nice if everyone kept a modestly sized signature.
wmoore said:
Page-long signatures seem to be getting more prevalent, sadly. Not great reading on a 1280x800 laptop.
Click to expand...
Click to collapse
XDA Signatures: The new Geociities
morell2 said:
it now work but all data delete!
i do unroot and back to stock with rootkit 1.5.2 and after it is work!
Click to expand...
Click to collapse
wat?
When you oem unlock, data is deleted, it tells you that. Otherwise, no idea what you're talking about.
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
evonc said:
Known issue about the bootloader. Have to be connected to a computer via USB to be able to boot into recovery. if you have a working system partition you can use a script or other apps that will boot you into recovery.
Also the bootloader will freeze if you try to boot into it via the buttons if you are connected to a power outlet via USB
Sent from my Nexus 7
Click to expand...
Click to collapse
wmoore said:
That's interesting. I pretty much always make sure I'm plugged in before going into recovery / bootloader anyway (I'm paranoid about running out of battery mid-operation). I also pretty much always use adb reboot recovery, etc rather than hardware buttons.
Click to expand...
Click to collapse
Not neccessarily true. I use an app called Quick boot. I can boot into recovery from it with Ease. Lets me set up Widgets/icon for recovery and I have one for reboot. No need for me to hook up to pc. Anywhere at anytime I can boot into recovery on my Nexus 7. I can also set one up for bootloader. If someone gets stuck on bootloader screen, the hardware button press for reboot works to get out of there.
They have a free version of the app and it works perfectly. Check it out. No need to run to a pc everytime you want to flash a rom or something. Battery is nothing to worry about. As long as you have 50%(really even less than that), you good to flash, wipe, or what ever.
demandarin said:
Not neccessarily true. I use an app called Quick boot.
Click to expand...
Click to collapse
Me too. Though I'm old school and still like to type commands rather than point and click. I'll be looking at Quick Boot but still go to PowerShell (which I always have open) and type adb reboot.:silly:
All the various apps that offer rebooting options will work as they are still executing the same terminal commands that you would've had to type in in order to reboot it.
The issue is that you would still require a working system partition in order to boot into recovery (stock/twrp/cwm) without any USB connection. Incase of a soft brick, you will need to connect to a computer in order to get into recovery so i would suggest people make sure they have one nearby when they're flashing stuff.
I just went through this. I boinked my setup and it was bootlooping. I couldn't get into CWM.
Just press and hold Power+VolDwn+VolUp until you get into the stock bootloader. Now plug in your USB to to a PC.
Stay in the bootloader. Mine actually kinda froze but it will unfreeze after a while. Don't select anything. Just stay there.
Now you can use Fastboot commands to reboot into CWM. ADB only works when the phone is on.
I think the command is "fastboot reboot recovery".
This will put you in CWM. You can also take this opportunity to reflash your recovery here too. I reflashed mine just to be on the safe side before rebooting it.
Sent from my Nexus 7 using xda premium
Hi everyone,
I started to use custom roms about some months ago, and I'm facing my biggest problem right now, hope someone can help me.
I flashed my phone via TWRP Custom recovery with CM10.1 and one day, suddenly the pin (that little entering for the charger and usb cables) stopped working, so I couldn't charge my phone in any "normal" way, I started using a direct battery charger. But today I flashed my phone with another version of CM and forgot to wipe data/cache, so now it's stucked in the CM boot animation. Thing is, I can't even access to recovery mode to flash again because for some reason, everytime I turn my phone off, it turns on automatically. Without pressing any button, and it doesn't give me time to do the vol-/home/power combo. I can't use any direct cable alternative either for what I described above. So I was wondering if some of you had a similar problem and can give me a hand with this. I'd be very much appreciated it.
Many thanks and greetings from Perú!
unotresocho.
unotresocho said:
Hi everyone,
I started to use custom roms about some months ago, and I'm facing my biggest problem right now, hope someone can help me.
I flashed my phone via TWRP Custom recovery with CM10.1 and one day, suddenly the pin (that little entering for the charger and usb cables) stopped working, so I couldn't charge my phone in any "normal" way, I started using a direct battery charger. But today I flashed my phone with another version of CM and forgot to wipe data/cache, so now it's stucked in the CM boot animation. Thing is, I can't even access to recovery mode to flash again because for some reason, everytime I turn my phone off, it turns on automatically. Without pressing any button, and it doesn't give me time to do the vol-/home/power combo. I can't use any direct cable alternative either for what I described above. So I was wondering if some of you had a similar problem and can give me a hand with this. I'd be very much appreciated it.
Many thanks and greetings from Perú!
unotresocho.
Click to expand...
Click to collapse
Press recovery combos when your turning off, see if that works, you might just be holding power too long and it turns on again
No usb at all? If you can connect with adb, you can reboot to recovery that way.
Combo.
unotresocho said:
Hi everyone,
I started to use custom roms about some months ago, and I'm facing my biggest problem right now, hope someone can help me.
I flashed my phone via TWRP Custom recovery with CM10.1 and one day, suddenly the pin (that little entering for the charger and usb cables) stopped working, so I couldn't charge my phone in any "normal" way, I started using a direct battery charger. But today I flashed my phone with another version of CM and forgot to wipe data/cache, so now it's stucked in the CM boot animation. Thing is, I can't even access to recovery mode to flash again because for some reason, everytime I turn my phone off, it turns on automatically. Without pressing any button, and it doesn't give me time to do the vol-/home/power combo. I can't use any direct cable alternative either for what I described above. So I was wondering if some of you had a similar problem and can give me a hand with this. I'd be very much appreciated it.
Many thanks and greetings from Perú!
unotresocho.
Click to expand...
Click to collapse
Use key combos mate... and after the phone vibrates, release only power button for avoiding the autorestart :fingers-crossed:
Hi, thanks all for your advices. I try em all but with no sucess. Though, something weird happened today. After the battery completely drained I tried charging it with the my regular charger, the cable to the wall one, and the phone vibrated, like it recognized it, but didn't turn on. Just vibrated. So I tried again using my micro USB to PC cable and the phone vibrated again when I plugged in to the USB port, but didn't turn on either, nor the PC recognized the device. Don't know if this is good or bad :S
If you have any more ideas, please let me know.
Thanks!
Unotresocho.
AlexGardunio said:
Use key combos mate... and after the phone vibrates, release only power button for avoiding the autorestart :fingers-crossed:
Click to expand...
Click to collapse
I'm trying this, but it keeps auto restarting. I'll describe what I'm doing, maybe there's something wrong:
1. Insert the battery.
2. Phone vibrates, I press Vol-/Home/Power and Samsung Galaxy S3 mini shows.
3. Keep pressing the combo and the phone turns off
4. Release the power button
5. Phone vibrates and again shows the Samsung logo and then the CM boot animation
Turn off again and same.
Thanks for the advice!
Hi again, I managed to get to "Odin Mode", the recovery that comes by default with the phone. Don't know why if I had TWRP installed. Does anyone know if it's gonna help me in some way? Remember I can't use a cable
Thanks!
How did you get into "Odin Mode"? Are you sure the cable is not working when the phone is in download mode?
Got into it by doing the button combo, tried several times and it was tricky but finally got it. And yeah I quickly connected to the computer (I have a Macbook but I also try on a PC) neither of them recognized it. Don't know what else to do
Try wireless adb.
When connected to computer:
Code:
adb shell
su
reboot recovery
As far as I know the phone should not vibrate everytime you put battery back. But if you're able to go into odin you should be able to go into recovery (unless volume up key is damaged). But... while in odin... you can go back to stock rom and that should solve lots of your problems mate.
tys0n said:
Try wireless adb.
When connected to computer:
Code:
adb shell
su
reboot recovery
Click to expand...
Click to collapse
Hi tys0n, thanks for your suggestion. I did a little research and found that to connect the phone on adb wirelessly I'd need a previously installed app. Do you know any other way to get it?
Many thanks!
unotresocho said:
I did a little research and found that to connect the phone on adb wirelessly I'd need a previously installed app.
Click to expand...
Click to collapse
You also need a working rom.
If the usb connector on the phone is broken, you can buy another one for 4$ on ebay, but you'll need to solder it and it's a smd component with small pins, so it may be difficult.
You can also try to reboot your phone in safe mode:
http://skp.samsungcsportal.com/integrated/popup/FaqDetailPopup3.jsp?cdsite=uk&seq=898277
http://androidjinn.com/boot-android-4-1-safe-mode.html
deconectat said:
You also need a working rom.
If the usb connector on the phone is broken, you can buy another one for 4$ on ebay, but you'll need to solder it and it's a smd component with small pins, so it may be difficult.
You can also try to reboot your phone in safe mode:
http://skp.samsungcsportal.com/integrated/popup/FaqDetailPopup3.jsp?cdsite=uk&seq=898277
http://androidjinn.com/boot-android-4-1-safe-mode.html
Click to expand...
Click to collapse
Yeah, thats true. A working system is needed.
Just a question.. When you try to enter recovery (vol+/home/power), have you tried to keep pushing when it reboots?
Have you tried to connect usb in download mode (vol-/home/power) to see if Odin detects it?
Whiteout a being able to synch to your computer or accessing recovery mode youre not gonna be able to restore your phone. Your best bet is buying a new micro usb cable (they are inexpensive) and restore using Odin.
tys0n said:
Yeah, thats true. A working system is needed.
Just a question.. When you try to enter recovery (vol+/home/power), have you tried to keep pushing when it reboots?
Have you tried to connect usb in download mode (vol-/home/power) to see if Odin detects it?
Click to expand...
Click to collapse
Yeah, I keep pushing the buttons combo and it reboots again, it won't start to boot CM, just displays de Samsung logo and reboots. About the second question, I've tried connecting the computer while in Odin mode but it won't recognize it, I haven't tried with Odin itself open because my primary computer is a Macbook and don't have a PC with the Odin installed near to me all the time. Do you think it could recognize the device, despite the fact the whole PC doesnt?
Thanks!
Arrrroz said:
Whiteout a being able to synch to your computer or accessing recovery mode youre not gonna be able to restore your phone. Your best bet is buying a new micro usb cable (they are inexpensive) and restore using Odin.
Click to expand...
Click to collapse
Hi, I wish it'd be that easy! The problem is the pin entrance in the phone, not the cable. I have like 4 with me, but none of them works
unotresocho said:
Hi, I wish it'd be that easy! The problem is the pin entrance in the phone, not the cable. I have like 4 with me, but none of them works
Click to expand...
Click to collapse
Oh, I see. You mention you could access odin mode, Im not familiar with it, but maybe it is possible that you could flash TWRP again, or CWR from the odin recovery? Also if you don't mind me asking, do you know how did the phone's pin got damaged?
I'm starting to thing you aint got a recovery at the moment. I've seen this type of thing before. Problem is, if you can't get odin to work you won't be able to solve it :/
Arrrroz said:
Oh, I see. You mention you could access odin mode, Im not familiar with it, but maybe it is possible that you could flash TWRP again, or CWR from the odin recovery? Also if you don't mind me asking, do you know how did the phone's pin got damaged?
Click to expand...
Click to collapse
I have no idea. I didn't fall or anything, it just stopped working one day. I thought it had to do with a "software" thing more than hardware, because I was using CM 10.1 and of course it wasn't official, it had bugs. I actually was trying to go back to CM10 to see if that was the problem but I got stuck here.
Okay, so, I know it's possible to fix this, it has to be. And let me explain why I can conclude this.
1.) I can access Philz recovery but ONLY when forcing the phone to hard reset via buttons.
2.) The touchscreen works in the recovery when resetting but doesn't go to the main menu or anything to restore a backup.
3.) The phone will recognize adb commands from the computer, but since the touches don't work when booted I cannot select the "allow this computer" prompt.
4.) The phone boots into the CM11 ROM and the buttons work (I can change volume, take screenshots, and access power menu.)
So, I'll explain what happened. I tested a boot.img for Quarx and flashed it. I didn't reboot my phone, just let it stay on. It worked and everything, but a little bit after church it rebooted on me and showed the CM setup menu. I was like, "What? Okay..." So I was going trying to make it work, but I realized the touchscreen wouldn't respond to my touches. I locked/unlocked the screen, rebooted, all that good stuff, and none of it worked. So, here's the damage done.
1.) I can't touch anything on the screen. It won't respond to touches.
2.) I cannot access recovery, only hard reset.
3.) I cannot approve adb commands because I need to hit "allow" on the screen. (The prompt does come up though)
So, I have a phone that boots, responds to hardware actions, and can recognize adb commands, but won't accept them unless I say "allow." I can access recovery but only when factory resetting through holding Power + VOL DOWN when booting. The touchscreen works in recovery, but it won't do any actions (back, home, etc.) because it's resetting. After resetting it boots instantly, and voila, my problem remains.
So in short, I need a way to bypass that "authentication" for adb, because in order for fastboot to recognize my device I need to run adb commands to set it up (since that's gone too now). That, or, I need to find a way to access Philz recovery without having to use the touchscreen. It's so frustrating because the one button I need to press is literally right in front of my face, on my screen, but it won't respond to my input.
Does anybody here have any suggestions? I haven't been able to flash a KDZ successfully, I don't know why. It never works for me on this phone. I was a pro at it on the L9. School begins in a week and I need to have a phone that works, for transportation and such. I'm not really at a point to buy a phone right now either since I'm focusing on buying my first car (yay I guess).
If anyone can help I'd really appreciate it. In fact, I'm even willing to donate money to whomever can point me in the right direction.
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
follow this guide and reflash KDZ
Ilxaot said:
Okay, so, I know it's possible to fix this, it has to be. And let me explain why I can conclude this.
1.) I can access Philz recovery but ONLY when forcing the phone to hard reset via buttons.
2.) The touchscreen works in the recovery when resetting but doesn't go to the main menu or anything to restore a backup.
3.) The phone will recognize adb commands from the computer, but since the touches don't work when booted I cannot select the "allow this computer" prompt.
4.) The phone boots into the CM11 ROM and the buttons work (I can change volume, take screenshots, and access power menu.)
So, I'll explain what happened. I tested a boot.img for Quarx and flashed it. I didn't reboot my phone, just let it stay on. It worked and everything, but a little bit after church it rebooted on me and showed the CM setup menu. I was like, "What? Okay..." So I was going trying to make it work, but I realized the touchscreen wouldn't respond to my touches. I locked/unlocked the screen, rebooted, all that good stuff, and none of it worked. So, here's the damage done.
1.) I can't touch anything on the screen. It won't respond to touches.
2.) I cannot access recovery, only hard reset.
3.) I cannot approve adb commands because I need to hit "allow" on the screen. (The prompt does come up though)
So, I have a phone that boots, responds to hardware actions, and can recognize adb commands, but won't accept them unless I say "allow." I can access recovery but only when factory resetting through holding Power + VOL DOWN when booting. The touchscreen works in recovery, but it won't do any actions (back, home, etc.) because it's resetting. After resetting it boots instantly, and voila, my problem remains.
So in short, I need a way to bypass that "authentication" for adb, because in order for fastboot to recognize my device I need to run adb commands to set it up (since that's gone too now). That, or, I need to find a way to access Philz recovery without having to use the touchscreen. It's so frustrating because the one button I need to press is literally right in front of my face, on my screen, but it won't respond to my input.
Does anybody here have any suggestions? I haven't been able to flash a KDZ successfully, I don't know why. It never works for me on this phone. I was a pro at it on the L9. School begins in a week and I need to have a phone that works, for transportation and such. I'm not really at a point to buy a phone right now either since I'm focusing on buying my first car (yay I guess).
If anyone can help I'd really appreciate it. In fact, I'm even willing to donate money to whomever can point me in the right direction.
Click to expand...
Click to collapse
I hate to say it but Factory Reset appears to be your only option for a fix.
Maybe this is a long shot but check out this thread
shinobisoft said:
I hate to say it but Factory Reset appears to be your only option for a fix.
Click to expand...
Click to collapse
Reset doesn't fix it because the boot.img is still the messed up one.
shinobisoft said:
Maybe this is a long shot but check out this thread
Click to expand...
Click to collapse
I cannot enable USB debugging to use that since the screen doesn't work and it reset itself.
gdjindal said:
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
follow this guide and reflash KDZ
Click to expand...
Click to collapse
I've tried that but it doesn't work for me. I need someone that can do it for me or something, because the KDZs never flash
@Ilxaot
are able to use philz??? fully...means is touch working on philz???
if yes then
you can put aroma file manager there...and in root of it in default.prop
change the lines
ro.adb.secure=1
ro.secure=1
to
ro.adb.secure=0
ro.secure=0
and reboot
now you have adb access without any confirmation required....
this is possible only if philz is working...
best luck...
and remove every possible LG driver from your pc
then reboot
connect to the internet
dont install drivers manually
let windows find the drivers if it doesnt find one.
then just reboot
after rebooting install drivers manually.
this works form me everytime.
k2wl said:
@Ilxaot
are able to use philz??? fully...means is touch working on philz???
if yes then
you can put aroma file manager there...and in root of it in default.prop
change the lines
ro.adb.secure=1
ro.secure=1
to
ro.adb.secure=0
ro.secure=0
and reboot
now you have adb access without any confirmation required....
this is possible only if philz is working...
best luck...
and remove every possible LG driver from your pc
then reboot
connect to the internet
dont install drivers manually
let windows find the drivers if it doesnt find one.
then just reboot
after rebooting install drivers manually.
this works form me everytime.
Click to expand...
Click to collapse
The only way I can boot into Philz is when it's factory resetting. When it's resetting, it shows the recovery and everything, but it's just resetting. There are no options to flash anything and such. It just resets and reboots.
EDIT - If I could get a KDZ to flash, I'd be set. When I connect my phone in laf mode (s/w mode) my computer doesn't recognize it. It says it's an unknown USB device, and shows a warning symbol next to it in the device manager. If I could get that fixed, I might be able to flash!
The recovery you use was not ok
Its gave me same problem when i try it,thank God i can enter download mode to flash KDZ and back to TWRP.
But what that is amazing me about your is that its cant do what other D415 does why? did your own D415 is special.
Also another thing is USB debugging,If you using CM11 by Quartz it was enable by default in that rom
4peace1 said:
The recovery you use was not ok
Its gave me same problem when i try it,thank God i can enter download mode to flash KDZ and back to TWRP.
But what that is amazing me about your is that its cant do what other D415 does why? did your own D415 is special.
Also another thing is USB debugging,If you using CM11 by Quartz it was enable by default in that rom
Click to expand...
Click to collapse
Yes but I still need to accept the prompt asking if I want to allow the computer to access the phone, which I cannot do because the screen does not respond.
How did you manage to flash the KDZ? I know it will be fixed if I can flash it, but I'm not having any luck flashing it! It keeps saying that the device is unknown, even though I've installed and uninstalled the drivers countless times.
Ilxaot said:
Yes but I still need to accept the prompt asking if I want to allow the computer to access the phone, which I cannot do because the screen does not respond.
How did you manage to flash the KDZ? I know it will be fixed if I can flash it, but I'm not having any luck flashing it! It keeps saying that the device is unknown, even though I've installed and uninstalled the drivers countless times.
Click to expand...
Click to collapse
I used this file here http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I entered download mode by remove my battery,unplug cable,
Then insert the battery back and press volume up key(hold it ),then insert the usb cable
after seen download headline then press power key it will take you to firmware update
4peace1 said:
I used this file here http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
I entered download mode by remove my battery,unplug cable,
Then insert the battery back and press volume up key(hold it ),then insert the usb cable
after seen download headline then press power key it will take you to firmware update
Click to expand...
Click to collapse
I tried that guide last night. The LG tool just has a bunch of question marks instead of text, is that normal?
Ilxaot said:
I tried that guide last night. The LG tool just has a bunch of question marks instead of text, is that normal?
Click to expand...
Click to collapse
yes
4peace1 said:
yes
Click to expand...
Click to collapse
Okay, I'll keep trying. When you booted into download mode, did your computer say the USB device was unknown?
Ilxaot said:
Okay, I'll keep trying. When you booted into download mode, did your computer say the USB device was unknown?
Click to expand...
Click to collapse
nope may you need to change the cable or try another port
4peace1 said:
nope may you need to change the cable or try another port
Click to expand...
Click to collapse
Can you give me the link to the kdz you used? I feel that's the problem. It gets stuck at 2%, and another user said he changed KDZs and it worked fine. I got my computer to recognize it, now I just need it to flash it lol.. It's really depressing how something as incredibly stupid as a KDZ flash is holding me back, and nobody's suggestions seem to be working. About to just give up and not even care about mobiles anymore >.<
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW015106432109876543213/D41010c_00.kdz
this is a kdz for d410 indian variant.
i dont know your model no.
k2wl said:
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW015106432109876543213/D41010c_00.kdz
this is a kdz for d410 indian variant.
i dont know your model no.
Click to expand...
Click to collapse
I actually just fixed it as you responded! Thanks mate!
you are welcome...so what about a nice unbricking guide from your experiences????
i think others will contribute so that we can make a good unbricking thread for l90...
k2wl said:
you are welcome...so what about a nice unbriking guide from your experiences????
i think others will contribute so that we can make a good unbricking thread for l90...
Click to expand...
Click to collapse
The guide that I followed was the one about flashing KDZs in thy general section. The problem I had was that my KDZ that I downloaded was corrupt somehow, so I had to find a working one!!
So I've been an idiot and am stuck. Maybe someone can help me here?
The issue with my Note for a while now is that the home button is broken and it's just not worth fixing (probably, I haven't really checked what it would cost), but then I could work around it with a 'software home button'. But here comes the idiot in me: I've flashed a new rom, but forgot to wype data and cashes and now I'm stuck at the boot screen while at the same time I can't get to recovery because of the broken home button. Duh..
Is there any way out of this?
Vathek said:
So I've been an idiot and am stuck. Maybe someone can help me here?
The issue with my Note for a while now is that the home button is broken and it's just not worth fixing (probably, I haven't really checked what it would cost), but then I could work around it with a 'software home button'. But here comes the idiot in me: I've flashed a new rom, but forgot to wype data and cashes and now I'm stuck at the boot screen while at the same time I can't get to recovery because of the broken home button. Duh..
Is there any way out of this?
Click to expand...
Click to collapse
try executing the command "adb reboot recovery" while in a boot loop.
Thanks. I had to google first what you meant by that, but I think I figured it out.
Still, my Note is not recognized by the computer, i.e. "adb devices" returns nothing. It's not a driver issue either, as there are no unknown devices in the device manager.
Looks like I'm out of luck here..
If u can get into dl mode (maybe a jig is needed) then flash stock wipe rom using odin. Search on wipe rom if needed more info.
Sent from my GT-N7000 using Tapatalk 2
Thanks guys, the jig probably would have done it. But in a rush of adventure I opened the thing up to see if I could get at the ribbon cable that connects the button. I didn't quite get there because I couldn't get the screen off without breaking it, but now that I've put it back together it won't even turn on anymore. I guess I totally wrecked it now, oh well.. :silly: