Related
I flashed the Cyanogen 7 Rom to my phone, and it worked great up until last night...
Last night, I go to check my phone and realize that it is stuck at the "X" displayed when booting up. Also, either the proximity or light sensor (not sure which one), is dimly lit red.
The phone will still boot into fastboot, and is recognized by fastboot when connected to a computer. However, adb will not recognize it. I've tried to recover using the PASSIMG.zip method but it just will not work.
Sorry to bother you guys, but I don't know what to do next. And i'm pretty new to rooting and using the SDK, so please go easy on me. lol. Hopefully someone out there can steer me in the right direction. Any help is greatly appreciated.
Do you have a nandroid backup you can flash from recovery? If not...why not?
If all else fails you can always try loading a ROM using fastboot. You'd have to unlock your Bootloader first though, if you haven't already. Which Custom Recovery are you using btw?
Yeah, I have a Nandroid backup. I don't think it's on my SD card though, also I don't think it is a zip if that matters.
And the custom recovery I have is Clockwork.
Lol, this may be a dumb question, but how can I be sure that my bootloader is unlocked?
Nevermind. I think It's bricked, All it will do is flash a red light in the top left hand corner. Please say I'm wrong though...
You would know if you'd unlocked the bootloader.
Have you been in the fastboot mode yet? It's the white background with three Androids on the bottom. This is how you unlock the bootloader.
There should be a guide on how to unlock the bootloader on the Wiki, I'll go find it...
Once you've done that, you can use ADB to try and restore your Nexus using this method. This method has worked for me everytime I've used it.
I'll edit my post when I've got the unlocking bootloader post.
EDIT: http://forum.xda-developers.com/wik...uides_&_Tutorials#ADB.2FFastboot.2FBootloader
The guide is under the heading 'Root', and starts with 'In order to Unlock the Nexus One's bootloader'.
Hope this helps!
If the screen with x had a lock on the bottom of it it was unlocked.
Sent from my Nexus One using XDA App
You don't need to unlock the bootloader to use adb. You unlock the bootloader to use fastboot...
Can you get into the bootloader our recovery?
Sent from my Nexus One using XDA App
Well there seems to be a turn of events! luckily, lol My phone still boots into fastboot, my bootloader is now unlocked, but I still cannot make a connection to ADB... I must be forgetting something or doing something wrong.
You cannot get a connection to ADB? Is ADB installed; did you install the Android SDK?
If you can get a connection, type adb devices into the command prompt/terminal. If the device is connected, it will say your phone's unique code then [devices]; if it is not connected it will say your phone's unique code then [offline].
danger-rat said:
You don't need to unlock the bootloader to use adb. You unlock the bootloader to use fastboot...
Can you get into the bootloader our recovery?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yeah I can still get into the Bootloader, but when I select recovery, it goes to the splash screen with the lock beneath it, and hangs up and gets SUPER warm to the touch after a few minutes lol
ADB probably isn't working because you aren't booting far enough into the system.
Try using fastboot to flash a new recovery image, and see if you can get into the new recovery...
Sent from my Nexus One using XDA App
When I type in adb devices It says "List of devices attatched" but then has nothing listed... but I'm pretty sure I installed the SDK; I used fastboot in the command prompt to unlock the bootloader.
I flashed a new recovery; I used cmd: "fastboot flash recovery recovery-RA-passion-v2.2.1.img" But I still can't get past the X with the pad lock screen...
Eeeek!
Might be time to give HTC a call.
I know a few people who couldn't flash recoveries, and nothing seemed to work. They returned the phone, and HTC fixed for free...
Sent from my Nexus One using XDA App
Do you have the drivers installed for the phone?
Sent from my Nexus One using XDA App
Ahhhhh, That's exactly what I didn't want to hear! Haha, well I guess there isn't any other way to try and get past this screen is there?
I really didn't want to have to bring HTC into the equation, haha. But, do you think they will still fix the phone after I had It running Cyanogen? AND after I unlocked the bootloader?
I just want to make sure they will still do something about it and not just leave me in the cold with a really nice looking paper weight...
albundy2010 said:
Do you have the drivers installed for the phone?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I should, I don't remember deleting them... How would I go about checking?
It will show up in device manager as nexus one. No yellow exclamation point. I don't recall if they are needed for fastboot/adb etc. Its in the wiki though.
Sent from my Nexus One using XDA App
If you're using fastboot commands, the drivers must be installed.
Don't worry about the phone being unlocked. If you can't boot the phone in it's current state, neither can HTC. So the first thing they will do is a full re-image, which will also fix your problem. Then they will probably test it, and just return it to you, because they can't find a problem...
Sent from my Nexus One using XDA App
I've been searching and searching.
I have a dell streak 7 with 2.2.2. Its very corrupt. It won't save settings, gets multiple force closes, gets a wifi error and won't uninstall apps.
It won't even factory delete in stock recovery.
I'm baffled and need some help. I can't root get apps etc for some reason.
I need some help!
sent from my sense on crack MT4G Slide using xda premium
I'm reading up on adb and how to install it. Some pointers would be nice as I'm trying to help my friend who messed his thing up.
Thanks in advance whoever can help me.
Couple things id like to add to maybe help anyone who decides to help me.
Factory reset in the os as well as both in stock recovery do nothing.
Most of the apps force close.
he took his sd card out. I can use mine though if needed.
He doesn't care about any data lost.
Anything I delete or undo setting for example will be redone as soon as phone is rebooted or setting is closed.
Wifi says error.
It is a tmobile streak 7 my sim card does work and it gets a signal but nothing else does.
Some solutions I thought of is. Try to find a full stock os
Flash someone else nandroid.
Sbf to stock.
Hence why iam reading on adb. On my phone I use terminal emulator so I have no idea how to use sdk and adb.
Sorry if I. Sound noob. Iam to this device .
sent from my sense on crack MT4G Slide using xda premium
Why does everyone want to be spoon fed everything...
http://forum.xda-developers.com/showthread.php?t=1286295
Sent from my Dell Streak 7 using xda premium
keith.valdez said:
Why does everyone want to be spoon fed everything...
http://forum.xda-developers.com/showthread.php?t=1286295
Sent from my Dell Streak 7 using xda premium
Click to expand...
Click to collapse
Okay I Read this already. It doesnt help me very much. I have the fastboot drivers but I do not have fastboot.exe in the adk.
The ADK does not come with it, and I've searched for it and found nothing that would help me for a dell streak. So if you could post the link to the right fastboot becuase in cmd it tells me fastboot is not a recognized as a internal or external command,operable program or batch file.
I cannot use ADB becuase I cannot check usb debugging it unchecks after I exit the dev section. Yes my ADB is setup right I can use it on my mt4gs perfectly.
Im dling the nvflash method now.
Update.
NvFlash method did not work.
You are stuck if Read Only mode and you have to send it in
cdzo72 said:
You are stuck if Read Only mode and you have to send it in
Click to expand...
Click to collapse
I agree. Your symptoms sound very similar to what I was experiencing on my t-mobile Streak 7. I sent it to Dell for repair and it works great now. Takes about 2 weeks for the whole process.
Call Dell support and they will eventually tell you that you need to send it in after having you try several things over the phone. They will ship you a box and pay for the postage to send it to Mexico.
Good luck.
cdzo72 said:
You are stuck if Read Only mode and you have to send it in
Click to expand...
Click to collapse
How does one get into read only mode? I ask this because hopefully he won't make the same mistake again with me informing him.
sent from my sense on crack MT4G Slide using xda premium
BTW got adb and fast boot working. Cannot flash anything to the system. Dang it I hope dell will take this and fix it, I dont think he has all the paper work.
My nexus one cannot go through the splash screen during the boot process and keeps restarting over and over. The power button is not working on the device, so I can't use the recovery or any option in the bootloader that requires me to push the power button.
I cannot enable the debugging option, since I can't start the phone.
I was trying to use fastboot thingy, but it keeps coming with "FAILED (remote: signature verify fail)" or" FAILED (remote: not allowed)"
Any idea how to bring this phone back to life?
I'm experiencing the same thing, broken power button and endless bootloops. I'm rooted, but only on the most basic ROMs without any sort of way reboot into recovery. Any help would be great...
I would get power button fixed firstly, if I were you. Good luck anyway!
Sent from my Nexus One using xda app-developers app
Connect your nexus to a charger, when led turns on pull the battery out, when led turns off put the battery in before led shows up again.
After you put the battery in correctly, just long press the trackball to get into hboot
After that just use the recovery to wipe and flash a new rom
Sent from my Nexus One using Tapatalk 2
mihovil13 said:
Connect your nexus to a charger, when led turns on pull the battery out, when led turns off put the battery in before led shows up again.
After you put the battery in correctly, just long press the trackball to get into hboot
After that just use the recovery to wipe and flash a new rom
Sent from my Nexus One using Tapatalk 2
Click to expand...
Click to collapse
Okay, so I made it into hboot, but please explain how I can get into recovery without a power button to select recovery.
use trackball and volup/down
trackball to choose, volup/down for marking/selecting
Do you use blackrose?
If so, trackball works 100%
mihovil13 said:
use trackball and volup/down
trackball to choose, volup/down for marking/selecting
Do you use blackrose?
If so, trackball works 100%
Click to expand...
Click to collapse
I don't use Blackrose, my ROM is a very basic form of MIUI from earlier this year and I haven't updated it since. I thought I would be able to use the trackball in place of the power button as well, but so far it's not working. Is there any other way to boot into recovery or another way to use the trackball instead of the power button?
Once u get hboot, connect N1 to PC and try 'fastboot reboot-recovery' in CMD
Sent from my Nexus One using xda app-developers app
longbowz said:
Once u get hboot, connect N1 to PC and try 'fastboot reboot-recovery' in CMD
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I'm trying that now and getting the message that the command isn't recognized...
Sorry I was wrong about it. The option is reboot-bootloader so there seems to be no way to boot to recovery directly in your case.
As to the message u got, you need to install android boodloader driver so that fastboot may work. But it can only lead u to hboot, not further.
Sorry for bad news
Sent from my Nexus One using xda app-developers app
longbowz said:
Sorry I was wrong about it. The option is reboot-bootloader so there seems to be no way to boot to recovery directly in your case.
As to the message u got, you need to install android boodloader driver so that fastboot may work. But it can only lead u to hboot, not further.
Sorry for bad news
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Don't worry about it, It's cool... I loved this phone, had it since it came out back in January 2010, now I have to find a new one. I was checking out the HTC One S and X, and maybe the X+ if they ever release it, are those good upgrades to the Nexus One?
I'm not expert of hardware, but believe theses are way much better than N1 as you will have bigger screen, more cpu cores, larger RAM and internal storage size, and most impotant - ICS or jelly beans ROMs.
Sent from my Nexus One using xda app-developers app
longbowz said:
I'm not expert of hardware, but believe theses are way much better than N1 as you will have bigger screen, more cpu cores, larger RAM and internal storage size, and most impotant - ICS or jelly beans ROMs.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
I tried one out today at a local T-Mobile store, it's a very nice phone but sorta disappointed me with the lack of transferable SIM and Micro SD cards. I'm gonna do more research on it but it's shaping up to look like my N1's replacement... :crying:
Oh well, it's been really good. The Nexus One has been easily the best phone I've had thus far and for the longest (2 years and almost 10 months).
Thank you all for the help in trying to recover it.
Finally, I was able to reset the phone by using the SD card. The steps are outlined here:
http://forum.xda-developers.com/wiki/HTC_Nexus_One/Guides_&_Tutorials
quasiquasar said:
Finally, I was able to reset the phone by using the SD card. The steps are outlined here:
http://forum.xda-developers.com/wiki/HTC_Nexus_One/Guides_&_Tutorials
Click to expand...
Click to collapse
Hi there, I'm having the exact same problem as you.. I tried to follow the instructions on the link you gave but I'm stuck on the 3rd step: how can I transfer a file to my sd card? when I enter the fastboot and the computer is connected I can see on my n1 that it is written "fastboot usb" but the computer doesn't show me that it's recognizing it...
Help would be very much appreciated!
i tried all the tricks and methods but my mobile just doesnt power ON
what might be wrong ? please help
Hey guys, I do no not own this phone (just picked up a Nexus 5) but, my dad does. He has been waiting for MONTHS to get his hands on this. It is his first Android device and he was able to ditch his work iPhone for it. However, he has been having an absolutely horrible experience:
I was remotely walking him through setup (moto transfer with iCloud to gmail account, etc etc).
- He turned on his phone, set up wifi, entered account credentials, played around for a minute or two.
- After this, he was prompted for an update, I told him to accept it
- After he accepted it, the phone WILL NOT TURN on. It boots to the homescreen, says it is "activating" the device, then it needs to restart.
- When it restarts, he sees the following attached screenshot.
I am assuming this was the Kit Kat update. I know tons of people have had problems with this (yes, I read the forums before posting, even though it is not my device). However, everyone with problems seemed to be rooted/not on stock. He is COMPLETELY stock.
If he chooses to reboot normally, he gets the homescreen, activation, then, it turns off and goes back to the attached screen.
If he chooses recovery, it goes back to this screen.
I'm not sure how an OTA could jack a phone up that was completely stock.. But it has happened.
Is there anything I can do remotely to help him start using his new phone? As I said, he has been excited for months for this phone and now just wants to throw it against the wall.
Is this screenshot the fastboot screen? If so, can I use the "fastboot erase cache" command?
Any *detailed* answers would be greatly appreciated... I'd love to get this working for him ASAP.
Thanks everyone!
View attachment 2415287
This is a pretty horrible out of box experience for something he was so excited about. I'm hoping this is something I can just do while remotely controlling his PC... I feel bad for the guy
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
waiflih said:
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
Not having this phone myself, how do I flash a recovery if I can't access current recovery or boot? Can I flash with a locked bootloader? Is the screen my dad is seeing the fastboot screen?
Any ideas how a stock out of the box phone would encounter this?
Thanks!
Sorry it's just hard to not have a device and jump into this when there are a million threads and it is completely different than any device I've owned (also I have no hands on time with it).
Thanks again. The more details the better so that I can do this remotely.
Sent from my Nexus 5 using XDA Premium 4 mobile app
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
EmperorX said:
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which model/carrier of phone does your dad have?
Xatt said:
Which model/carrier of phone does your dad have?
Click to expand...
Click to collapse
He's on Verizon, 16gb.
So confused as to how this happens fresh out of the box. Don't know how it's possible. I'm determined to fix it for him today though so he doesn't have to wait even longer
Sent from my Nexus 5 using XDA Premium 4 mobile app
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
theraffman said:
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
waiflih said:
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
I'm assuming I can use any of the builds from verizon there? I'd like to get him to update OTA and see if it works this time or not... Was thinking about flashing one of the three 4.2.2 ones
EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
EmperorX I work for Moto. If you wouldn't mind providing the IMEI I'll get our engineers to take a look. You can PM me. Thanks!
I found this toolkit:
However, i'm assuming the fastboot menu will not work to just flash stock as you need to be in "Android or hboot"
The fastboot screen I took the picture of is not the same thing as hboot correct?
They are interchangeable terms. Hboot refers typically to an HTC bootloader
gunnyman said:
They are interchangeable terms. Hboot refers typically to an HTC bootloader
Click to expand...
Click to collapse
Awesome, looks like I may be able to fix this for him after all. Just need to remotely get androidsdk and adb setup on his computer with RSDlite as backup if this toolkit doesn't work and I *should* be able to make this happen. I think i've got enough info to do this now. Thanks guys!
EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
theraffman said:
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He was on the phone with Motorola "tier 2" support this morning for 3 hours. Their solution was to order a new phone and expedite shipping and return the old one when it gets here. I'm going to try this way first. They said this happens to "1 in 10,000" people. Lol, he's a lucky guy!
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
Sounds like the phone's partitions are all jacked up. Get a new phone is the solution.
EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
what probably happened was your dad never activated the phone then tried to take an ota or something like that and it got all jacked up. Alternatively, he could have (for some reason) gotten the 4.4 OTA even though the phone was on original stock FW. This could have f'd the phone up if it skipped the 4.2.2 OTA. If you need to help you dad out, download teamviewer or logmein (remote computer access programs) and just guide him through when to plug the phone in etc.
Not sure about the error you are getting but it could be because you are flashing the wrong FW for the phone, possibly an older FW or an updated FW and the order you are flashing it could be causing the error. You can fix this relatively easily if you were more familiar with fastboot. I can try and walk you through some stuff as well on gchat if you need some help. I could also remote into your dads computer and do everything that needs to be done (he could then remove my ability to remote in clearly). All that being said Im fairly busy so just answering some questions for you would be easier but more time consuming for your dad. For starters, you probably should be flashing the 4.2.2 FW found on sbf. it is the middle fw for verizon on the list. You also can probably just use rsdlite since he hasn't set the phone up. It is super easy. Just go to the thread for rsd lite back to 100% stock and you will be good to go. Then make sure he activates and sets the phone up and everything before he takes the OTA this time.
BACKGROUND: So i rooted my kindle using this tutorial http://www.youtube.com/watch?v=hUW6KARo8Y4 and it worked fine... up until i tried to put the new os. This was a very long time ago and you can follow my progress in my old forum http://forum.xda-developers.com/showthread.php?t=2536008&page=4 (which did not fix it.) I decided i need a new start so i made this new forum.
Okay so heres the problem: When i boot up my kindle, it shows the regular kindlefire logo (not fire fire fire) and then a red screen slides by and it boots into fastboot.
*I do have access to a factory fastboot cable*
18lo said:
BACKGROUND: So i rooted my kindle using this tutorial http://www.youtube.com/watch?v=hUW6KARo8Y4 and it worked fine... up until i tried to put the new os. This was a very long time ago and you can follow my progress in my old forum http://forum.xda-developers.com/showthread.php?t=2536008&page=4 (which did not fix it.) I decided i need a new start so i made this new forum.
Okay so heres the problem: When i boot up my kindle, it shows the regular kindlefire logo (not fire fire fire) and then a red screen slides by and it boots into fastboot.
*I do have access to a factory fastboot cable*
Click to expand...
Click to collapse
Its a really simple fix. Just making sure, this is codename tate? Turn off the kindle. Download the restore image tool for the kindle on the development page where you get ROMs. After that's downloaded plug in the fast boot cable to the PC and your kindle. Turn the device on, run the bat file from the image tool, and then you want to do 4, then the one that restores to the original bootloader, don't know what number. Then hit 1. After that you have a brand new kindle. And reboot with a regular cable.
18lo said:
BACKGROUND: So i rooted my kindle using this tutorial http://www.youtube.com/watch?v=hUW6KARo8Y4 and it worked fine... up until i tried to put the new os. This was a very long time ago and you can follow my progress in my old forum http://forum.xda-developers.com/showthread.php?t=2536008&page=4 (which did not fix it.) I decided i need a new start so i made this new forum.
Okay so heres the problem: When i boot up my kindle, it shows the regular kindlefire logo (not fire fire fire) and then a red screen slides by and it boots into fastboot.
*I do have access to a factory fastboot cable*
Click to expand...
Click to collapse
I told you last time you flashed the wrong bootloader. The video is for an 8.9. You seem to not be able to make up your mind which mod you tried first but you have issue that are not repairable.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
I told you last time you flashed the wrong bootloader. The video is for an 8.9. You seem to not be able to make up your mind which mod you tried first but you have issue that are not repairable.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Um, you sure he hard bricked it? He said it's going to a red screen then fastboot, if that was the case and the pc can detect it he should be able to reflash the bootloader. Then again i didnt really read the thread he posted, just kinda glanced through it.
stunts513 said:
Um, you sure he hard bricked it? He said it's going to a red screen then fastboot, if that was the case and the pc can detect it he should be able to reflash the bootloader. Then again i didnt really read the thread he posted, just kinda glanced through it.
Click to expand...
Click to collapse
You might try reading the original thread then.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
You might try reading the original thread then.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok after reading that i'm a bit confused becasue it seems suggestions were being thrown all over the place. I see it says he thought he flashed firefirefire, but as far as i know, flashing that would have resulted in the device not even wanting to power on since its not designed for our device and wouldnt turn on.
I'm willing to play ball and see where this goes just to see whats going on. If you can get fastboot to recognize the device try running "fastboot -i 0x1949 getvar product" and tell me what it hands off, i want to know once and for all that this is a 7" hd model and that will tell me.
LinearEquation said:
I told you last time you flashed the wrong bootloader. The video is for an 8.9. You seem to not be able to make up your mind which mod you tried first but you have issue that are not repairable.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i was able to remove the bootloader
Uh oh... I tried to use KFFirrstAid again and completely restore to 7.2.3 and i believe i have officially hard bricked my kindle. It does not turn on and the computer cannot detect it. Thanks for your help anyway
how did kffa manage to hard brick it???? Well if it is indeed hard bricked i would see about putting it to a good cause and see if @kurohyou wants it. He mapped out emmc pins for the 8.9" and kf2 so we can reflash teh bootloader via soldering a sdcard reader to the kindles motherboard, but he still needs a hard bricked kfhd 7 to map th epins out for this model. Downside is it will probably make the kindle's motherboard completely unusable because he has to unsolder the emmc chip to figure out the pin locations. He might be able to solder the emmc back on thought so you might actually get a working motherboard back if you get lucky. This would benefit the community as awkward as it is to ask.
stunts513 said:
how did kffa manage to hard brick it???? Well if it is indeed hard bricked i would see about putting it to a good cause and see if @kurohyou wants it. He mapped out emmc pins for the 8.9" and kf2 so we can reflash teh bootloader via soldering a sdcard reader to the kindles motherboard, but he still needs a hard bricked kfhd 7 to map th epins out for this model. Downside is it will probably make the kindle's motherboard completely unusable because he has to unsolder the emmc chip to figure out the pin locations. He might be able to solder the emmc back on thought so you might actually get a working motherboard back if you get lucky. This would benefit the community as awkward as it is to ask.
Click to expand...
Click to collapse
ill see what i can do. i certainly have no use for it.