basically, before you guys judge, why would i need a pattern bypass, let me get through the story.
Basically, my tenant couldnt pay her rent, so she decided to give me half and leave. when she left, she also left her dell streak. i gave her a call and she told me i can just have it. when i tried to turn it on, it wouldnt so i charged it. waited a while, say 6 hours, then when i got back to it, there was a pattern lock. called her again but unfortunately, her cell phone line got deactivated. its been 2 days, and ive been trying but no luck.
basically, i just need a program, software, anything? lol. to bypass this because i want to sell it, or maybe try to fall in love with it
*things i have tried*
[1.] Vol up + Power
~brings me to (stock??) recovery (im guessing?) with 5 choices.
0. Boot Up
1. Factory reset (User data only)
2. Software upgrade via update.pkg on SD card
3. Factory reset (User data and Internal Tablet storage)
4. Power off
~Chose #1 which failed
~Chose #3 also failed
both booted up perfectly and still showed the pattern unlock screen.
[2.] Followed a guide
~i basically treated the streak like it was bricked, so i fallowed a guide from illdill (sorry i forgot the link) but it was something related to nvflash and using it to flash images 2-21 on the dell streak 7.
~this method also failed, and also booted up perfectly.
*[3.] Try to put HoneyStreak RC 2.1*
~i get the error "Formatting partition 2 BCT please wait.. FAILED!"
idk what i means but all i know is that when i used the search button, i guess peoples who ask about it and have trouble about it, they get ignored. they try to bump, but yet no response. I read from post 427 to almost 560. none was answered. if there is a way out there. please help me ;(
only 2 methods i tried. anyone else? thanks in advance xda users. quick responses that arent usually nonsense gets a thank button clicked from me
jayjaypops said:
basically, before you guys judge, why would i need a pattern bypass, let me get through the story.
Basically, my tenant couldnt pay her rent, so she decided to give me half and leave. when she left, she also left her dell streak. i gave her a call and she told me i can just have it. when i tried to turn it on, it wouldnt so i charged it. waited a while, say 6 hours, then when i got back to it, there was a pattern lock. called him again but unfortunately, his cell phone line got deactivated. its been 2 days, and ive been trying but no luck.
basically, i just need a program, software, anything? lol. to bypass this because i want to sell it, or maybe try to fall in love with it
*things i have tried*
[1.] Vol up + Power
~brings me to (stock??) recovery (im guessing?) with 5 choices.
0. Boot Up
1. Factory reset (User data only)
2. Software upgrade via update.pkg on SD card
3. Factory reset (User data and Internal Tablet storage)
4. Power off
~Chose #1 which failed
~Chose #3 also failed
both booted up perfectly and still showed the pattern unlock screen.
[2.] Followed a guide
~i basically treated the streak like it was bricked, so i fallowed a guide from illdill (sorry i forgot the link) but it was something related to nvflash and using it to flash images 2-21 on the dell streak 7.
~this method also failed, and also booted up perfectly.
only 2 methods i tried. anyone else? thanks in advance xda users. quick responses that arent usually nonsense gets a thank button clicked from me
Click to expand...
Click to collapse
Try flashing Honeystreak (it completely erases the internal memory since it needs to repartition it) if you like Honeystreak, keep it, if you want stock, flash back. Hopefully that will work.
bluesy_92 said:
Try flashing Honeystreak (it completely erases the internal memory since it needs to repartition it) if you like Honeystreak, keep it, if you want stock, flash back. Hopefully that will work.
Click to expand...
Click to collapse
thanks for quick response, ill try and see, most of the things im reading are, i have to atleast have CWR. which i highly doubt she has. when i tried to explain to her what "rooting" means, lets just say she wasnt interested at all.
unfortunately, it didnt work. somethings about "Formatting partition 2 BCT please wait.. FAILED!" and doesnt go through, that makes method 3 = failed. unless someone out there has a different suggestion?
thanks in advance
Uh...it failed to format the partition? I don't think I've ever seen that happen.
I know this will sound stupid, since you are probably in the right forum, but where you said "streak" are you sure it was the 7 inch and not the 5? Also, you said you got into recovery by volume UP and power, but I think volume DOWN and power is stock recovery...maybe it had CWM installed by someone who has used it before? (the options sound like CWM) and in that case, someone may have changed something. Again, I'm shooting in the dark, but if it is a streak 5, or if it has CWM, it would be different than just a stock Streak 7 on the lockscreen. The streak 5 and 7 are not just different sizes of the same device - they run on a different chipset. The 5 has a snapdragon (I believe) and the 7 has a Tegra 2.
EDIT: You said Streak 7 in the title, so...I'm pretty sure you know it's a 7. In that case, I don't know why it won't flash :-/
bluesy_92 said:
Uh...it failed to format the partition? I don't think I've ever seen that happen.
I know this will sound stupid, since you are probably in the right forum, but where you said "streak" are you sure it was the 7 inch and not the 5? Also, you said you got into recovery by volume UP and power, but I think volume DOWN and power is stock recovery...maybe it had CWM installed by someone who has used it before? (the options sound like CWM) and in that case, someone may have changed something. Again, I'm shooting in the dark, but if it is a streak 5, or if it has CWM, it would be different than just a stock Streak 7 on the lockscreen. The streak 5 and 7 are not just different sizes of the same device - they run on a different chipset. The 5 has a snapdragon (I believe) and the 7 has a Tegra 2.
Click to expand...
Click to collapse
ahhh, thank you. first off, the partition, basically it looks like this (http://forum.xda-developers.com/showpost.php?p=15109690&postcount=425). i have no idea why it fails.
the only ways i could tell it "might be" a streak 7 is....
stock, Volume Up+Power is stock recovery menu. Volume Down+power is USB Fastboot. Has red letters as well.
now. is there anything visible or any button power combo where i would be able to find out if this was a dell streak 5 or 7? sorry for the nweb question.
*fyi, i know how CMW looks like, i have owned many android devices and... lets just say trust me... the Volume Up+Power looks like stock recovery and the only reason i say this is because it has 5 options, and 2 of them are Factory Reset.
Thanks again for quick response!
Other than the screen size, the capacitive buttons are layed out differently. On the streak 5, they are equally spaced, wheras the Streak 7 has them placed so that in landscape, they would all be under your thumb. The Streak 5 also has a removable battery, and the Streak 7 does not. If you check the back and it is smooth with a removable battery, it's a 5. If it is lightly textured without a removable battery, it is a 7.
Hope this helps
EDIT: And as far as the partition, I still don't know what would cause the problem. It might be best to ask someone with more NVFlash experience than me
bluesy_92 said:
Other than the screen size, the capacitive buttons are layed out differently. On the streak 5, they are equally spaced, wheras the Streak 7 has them placed so that in landscape, they would all be under your thumb. The Streak 5 also has a removable battery, and the Streak 7 does not. If you check the back and it is smooth with a removable battery, it's a 5. If it is lightly textured without a removable battery, it is a 7.
Hope this helps
EDIT: And as far as the partition, I still don't know what would cause the problem. It might be best to ask someone with more NVFlash experience than me
Click to expand...
Click to collapse
perfect bluesy_92. you've helped me so much already even thought my dell streak is still "unable to be used" now im for sure guarenteed this is a dell streak 7 (lol) since there is no removable battery and the c buttons are right under my thumb landscape wise.
as for the partition, would you help me figure out? ill sorta spam (not really) on the development thread for anyone who has nvflash experience to help me out with my streak.
as for others who click on this thread and do read and by any chance know any nvflash experience. please do help and just jump right in. thanks so much XDA community providers lets see if we can get through a bypass.
as of things to try
as of things to try in the morning when i wake up for work
the only thing im missing now is my adapter for my miniSD card to stick it in my streak and do the update.pkg file from the stock recovery menu. idk if it will bring me far because at work, i have internet access all day via phone (htc sensation) and i can try to keep update with my xda app but i have no desktop whatsoever.
jayjaypops said:
perfect bluesy_92. you've helped me so much already even thought my dell streak is still "unable to be used" now im for sure guarenteed this is a dell streak 7 (lol) since there is no removable battery and the c buttons are right under my thumb landscape wise.
as for the partition, would you help me figure out? ill sorta spam (not really) on the development thread for anyone who has nvflash experience to help me out with my streak.
as for others who click on this thread and do read and by any chance know any nvflash experience. please do help and just jump right in. thanks so much XDA community providers lets see if we can get through a bypass.
Click to expand...
Click to collapse
Well, I've heard of people getting devices that are locked in read-only, basically making them unable to be flashed. The fact that nothing is working scares me that this may be the case, but at the same time, I never experienced it, so I definately can't be sure. Someone who has may be able to tell you if you're stuck. If it is read-only, your only hope is Dell by that point :-/
That's the first thing I think you should find out. Because if it is locked in read-only, your case is pretty much closed at that point (and not in a good way, unless Dell helps you.) If you find out it's not, then I would try to figure out why Honeystreak isn't flashing properly.
You can try update.pkg - everything is worth a shot, but unlike flashing Honeystreak, I think it won't repartition or anything (updating through a .pkg is the way manufacturers release updates - it was not designed to be harmful to the users data, afaik) so that's not exactly a sure-thing. Don't let that stop you from trying it, though - when something can't be used at all, any idea is a good idea
bluesy_92 said:
Well, I've heard of people getting devices that are locked in read-only, basically making them unable to be flashed. The fact that nothing is working scares me that this may be the case, but at the same time, I never experienced it, so I definately can't be sure. Someone who has may be able to tell you if you're stuck. If it is read-only, your only hope is Dell by that point :-/
That's the first thing I think you should find out. Because if it is locked in read-only, your case is pretty much closed at that point (and not in a good way, unless Dell helps you.) If you find out it's not, then I would try to figure out why Honeystreak isn't flashing properly.
You can try update.pkg - everything is worth a shot, but unlike flashing Honeystreak, I think it won't repartition or anything (updating through a .pkg is the way manufacturers release updates - it was not designed to be harmful to the users data, afaik) so that's not exactly a sure-thing. Don't let that stop you from trying it, though - when something can't be used at all, any idea is a good idea
Click to expand...
Click to collapse
well, im not really trying to flash anything, i dont even care if its rooted or not, i just want it to be working basically. so my son can watch his elmo while i play my game or update my roms or watch my movies without him whining anything just to make it stock perfect again and this bypass to go through >__<"
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Are you sure you had it in apx mode ?
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Just put the image file into your fastboot directory and boot it from your computers hard drive ( fastboot boot cwm.img )
pyraxiate said:
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Are you sure you had it in apx mode ?
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Just put the image file into your fastboot directory and boot it from your computers hard drive ( fastboot boot cwm.img )
Click to expand...
Click to collapse
re read past posts?
pyraxiate said:
What happened when you tried nvflash ?
Did it push all of the partitions properly ?
Click to expand...
Click to collapse
this is what it looks like when i double click download.bat (http://forum.xda-developers.com/showpost.php?p=15109690&postcount=425) it gives me a FAILED!
pyraxiate said:
Are you sure you had it in apx mode ?
Click to expand...
Click to collapse
hold down Volume up + Volume down while plugging the USB cable in? Pretty sure i am because the first time i got prompted on my computer, i already downloaded the drivers, i just had to direct it to find the drivers, it said APX mode.
pyraxiate said:
I just recovered mine from a honeystreak flash and nvflash rewrites all partitions. Then try to fastboot push the system / recovery images.. After that you should be able to use cwm via fastboot to write a new rom ( I went back to streakdroid 1.3 ).
Click to expand...
Click to collapse
when you double click download.bat, after the img file 14 or 15 goes through, does your command screen suddenly disappear? whats your next step through that?
I flashed using these partition images ( Not the ones in the initial NVflash post) Maybe your image files were corrupted on download. Im glad someone uploaded them in 1 rar to ensure a clean set
Id start over from scratch by using this rar as your c:\Nvflash directory
http://www.multiupload.com/OM0VO9HBO9
See if those make a difference. After Nvflash completes the box will close, its normal. Use the pinhole to reset. From there I just used fastboot ( vol down and power ) to boot into cwm ( i can dropbox the image if you need it ). The command is : fastboot boot cwmimagename.img
from there you can format data/cache/system/dalvik/storage ( mine came back with an error not being able to format a few but try it anyway)
Mount SD card and copy something like the streakdroid zip to it. Using CWM's menus, install a zip from SDcard and choose it. It should run w/o error.
I had the Dell logo only stuck on boot after that , so I went into recovery and formatted user data only . From there it booted right up.
When you boot your streak, does it still boot into the original rom or does it just freeze on the Dell logo?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
pyraxiate said:
I flashed using these partition images ( Not the ones in the initial NVflash post) Maybe your image files were corrupted on download. Im glad someone uploaded them in 1 rar to ensure a clean set
Id start over from scratch by using this rar as your c:\Nvflash directory
http://www.multiupload.com/OM0VO9HBO9
See if those make a difference. After Nvflash completes the box will close, its normal. Use the pinhole to reset. From there I just used fastboot ( vol down and power ) to boot into cwm ( i can dropbox the image if you need it ). The command is : fastboot boot cwmimagename.img
from there you can format data/cache/system/dalvik/storage ( mine came back with an error not being able to format a few but try it anyway)
Mount SD card and copy something like the streakdroid zip to it. Using CWM's menus, install a zip from SDcard and choose it. It should run w/o error.
I had the Dell logo only stuck on boot after that , so I went into recovery and formatted user data only . From there it booted right up.
Click to expand...
Click to collapse
sorry for the late reply, i just barely got home from work. i just bought myself a 2 gig micro sd card, and the adapter to stick the micro sd card in the bigger sd card. im going to try the update.pkg. unfortunate of me, i tried to do it right away but its low battery just my luck. charging the streak 7 right now.
pyraxiate said:
When you boot your streak, does it still boot into the original rom or does it just freeze on the Dell logo?
Click to expand...
Click to collapse
not even, it would boot original rom with the users data still enabled. (the reason i say this is because, the pattern lock is still there) even when i tried the nvflash, it would boot right up to the pattern lock and with the same background she always had.
idea
since i now have an sd card, im going to try the "Restore your DS7" but the only thing thats stopping me is that it requires CWR which i dont have. ill try to work around it since my DS7 is recognized by fastboot and ADB. Also wanted to add another misfortune of mine, she does have debug mode on but fastboot should work rather than ADB. wish me luck.
if anyone has any other suggestions or ideas, please budge in. i dont mind at all. thanks for the help all!
lufc said:
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Click to expand...
Click to collapse
sorry lufc. thanks for moving. i apologize. just stressed out from real life events. arent we all ? aha. thanks and im sorry once again!
jayjaypops said:
since i now have an sd card, im going to try the "Restore your DS7"
Click to expand...
Click to collapse
failed, right when i typed adb devices, it shows my DS7 numbers, but when i type adb shell, i dont get ~# sign back. i get an error: Closed!
here i come nvflash. i shall try you again with the help of "pyraxiate" link he used to restore his DS7. wish me luck!
here i come nvflash. i shall try you again with the help of "pyraxiate" link he used to restore his DS7. wish me luck!
Click to expand...
Click to collapse
failed aswell, after double clicking restore.bat, i let it do its own thing, after it pushes p14.img file, it closes the command box right away, so i used an earring to turn off the device, unplugged from the usb, and yet, it still loads up pefectly with the same wallpaper and still the pattern lock... ughh, this is really frustrating!! ;'(
im trying one last step, before i call dell... (i dont even know if they'll replace this since im not the owner or the buyer of the product. unless they will? let me know)
my last step im taking is, im gonna use nvflash again, but this time im gonna use the WIFI DS7 partitions. hopefully it works. please almight lord! *sniff* begging. wish me luck. ill update
and as you already know what im going to say next, if anyone out there has any suggestions, ideas or plans. please help me out. might help others out in the community. thanks so much in advance
Related
I'm not a total noob to rooting as I've already rooted my G1 and am running cyanogen's mods for months now. My problem is on a different phone.
This dream was dropped in water months ago (that's when I purchased my 2nd on craigslist). The touchscreen wouldn't work so I was stuck at the setup screen. I read on many forums, xda included that it might eventually dry out and today I found that it was indeed working fine.
It works fine on stock 1.5 ota update crc1 but now that I rooted one I want this one rooted as well. This is where my problem starts. I'm trying to rollback using the dreaim.nbh found inthe latest "how to root" thread in the dev forum. Problem is I can't load the image. I powe up holding camera and power button, get to the multicolored bootloader, insstructions on the grey/whitish screen say press power button to load, and then I am stuck.
Power button does nothing and the phone is stuck on that screen until I pull the battery. Been through this process 5+ times, with redownloaded image (file is not corrupt) My concern is Ill end up bricking but I really want root. I'm think their might be water damage on the phone but everything else works fine.
Any suggestions for a workaround or a way to troubleshoot the problem? Thanks in advance!
-Air
nbh
heres a link to where you can get the nbh dwnload this one nd try agian.
http://coolpstuts.blogspot.com/2009/07/all-download-links.html
no dice
pistol thanks for the try but it didn't work. same 87.3mb file, rc29, same result.
the greyish white screen loads, but the update (rollback) never starts. Does anyone know of another way to load the dreaim.nbh image? or heard a similar issue?
are you sure you grabbed the t-mo image?? go to the original how to root your phone thread and grab the t-mo image, nothing has changed so there is no reason for us to have an updated thread other than to confuse people even more
my problem is not the rc29 image
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Was not implying that this thread would be a how-to and confuse people, merely that we have so many and people are constantly asking how to do something even though the steps didn't change. The physical abuse your phone has sustained "should" have no effect on the image flashing. I would suggest you format your card again(not in windows as windows seems to screw up a lot), so long as you are using the correct image and a fat32 formatted card you shouldn't have any problems, does the screen pop up and say "no image found"
airmaxx said:
tubaking, my problem is not the rc29 dreaim.nbh image. I have consistently found the same image in many threads on xda. my problem is that i cant get it to load. this thread was not created for general rollback issues and def not to confuse people with another how to.... i am trying to figure out why my US G1 (with a noted history of physical abuse) won't load the image.
Click to expand...
Click to collapse
hmmm, have you tried re-formatting your card?
trying it now
reformatted at home using gparted but I'll try paragon now that I'm at the office.
tubaking, thanks for the advice and willingness to help. it does not say no image found. It actually shows the steps that it needs to install including, radio_vz, and a few other things i cant recall right now...
hopefully the reformat will do the trick. I will try to format the entire card fat32 for now and then add my ext3 after. reporting back shortly....
still not working
so reformatted again to fat32, used paragon, gparted, and built in format on the G1 still the same result
grey white screen, reads the image.... then stuck at:
Code:
DREAIMG.nbh -
BOOTLOADER -
RECOVERY -
BOOT -
SPLASH1 -
SYSTEM -
USERDATA -
RADIO_VZ -
Press power button
to start update image
Press action button
to cancel update image
and then I'm stuck
So even after you press the power button to start the update, it just stays at that one screen and never gives any "ok"s next to any of the listings?
exactly
no oks, just hangs there
I've been letting it sit since before my last post, about 45 mins so far and still nothing. I may have imagined it but when i did this process last week it felt like it was getting hotter, but still nothing happened
also I remember doing this on my other G1 that is already rooted, so I know how easy this step should be
Stupid question, but are you making sure not to rename the original DREAIMG.nbh to anything else other than what it is? Some people make the mistake of thinking they have to rename it to update.zip or make the mistake of not leaving it in capital letters (although I don't know if that matters). You have said you have downloaded the file multiple times so I doubt this is the case but I'm just spitballing here
no rename
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
airmaxx said:
In my desperation I had considered that really stupid idea for a moment but thought better of it. I don't want to end up with a brick i haven't renamed it, consistently used dreaimg.nbh
Click to expand...
Click to collapse
I wasn't suggesting to rename it, I just wanted to make sure that you never had renamed it to anything but the original filename DREAIMG.nbh
its all good
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
airmaxx said:
directmatrix, I understood your post. I was just saying i had considered renaming it to update.zip in an effort to get something going. I appreciate the spitballing, maybe we'll hit something that I missed!
Click to expand...
Click to collapse
I re-read your original post and was curious as to whether the power button could be the culprit considering that its needed to flash the image. Perhaps the water may have damaged the power button interface. I can't imagine that it would be the problem considering your able to get into the rainbow screen via power+camera. Have you tried pushing it harder, many times, on the side etc?
i did, tried holding it for a 10 count, multiple presses, long press. I'm pretty sure the problem is not with the button itself because it works fine when I have the phone booted up and press power to turn it off.
When I first posted I was hoping someone might know of an alternative button combo that might have the same effect of loading the image from that greyish white screen
there is no way to write the image through adb right?
Streak 7 Stuck at Dell Logo
Formatted the System and Data and reflashed the system and boot.img files but now stuck at dell logo.
No power on key combination produces any other result.
Only have two options that I can think of.
1) Somehow boot from sd card
2) Get the nvida/tegra chipset sdk which I can't find a download for anywhere
Any other suggestions?
I posted it in the other thread
Sent from my Dell Streak 7 using XDA Premium App
thatruth132 said:
I posted it in the other thread
Sent from my Dell Streak 7 using XDA Premium App
Click to expand...
Click to collapse
Thanks, installing now. I called Dell and they are sending me a new one, but I would still like to resolve this so others don't have to do this.
Any tips on how to use this?
I am going to try the QDL tool that can be downloaded here: http://www.streakdroid.com/repairtool.zip
This may get me back up and running, we'll see. If so, I will post the procedure.
QDL is supposed to be a rom recovery utility that can communicate with the device in almost any scenario. Since ADB can see the device, I might have some luck.
Good luck
Sent from my Dell Streak 7 using XDA Premium App
illdill said:
I am going to try the QDL tool that can be downloaded here: http://www.streakdroid.com/repairtool.zip
This may get me back up and running, we'll see. If so, I will post the procedure.
QDL is supposed to be a rom recovery utility that can communicate with the device in almost any scenario. Since ADB can see the device, I might have some luck.
Click to expand...
Click to collapse
instead of going through all that just call dell.. play dumb and just say after the update you got stuck at the dell screen.. they will try to get it to boot in recovery but that wont work.. so then they will issue a warranty exchange.. and it's not a refirb they are sending.. it's the full retail package again I'm going to "forget" to send back the charger and have two.. I never send back the chargers to dell when I do a replacement.. so if they dont ***** about a $100 charger missing they wont ***** about a streak charger missing.. as a matter of fact with my old laptop I forgot to send the charger back and called them, they said "na, it's a minor part. Onky send it back if we contact you abaout it" They never did
But all this time you're doing all this.. you could have a new one on it's way to you with pretty much no questions asked.. just say you got the update.. it said it would reboot.. it rebooted and now youre stuck at the dell screen..
graffixnyc said:
instead of going through all that just call dell.. play dumb and just say after the update you got stuck at the dell screen.. they will try to get it to boot in recovery but that wont work.. so then they will issue a warranty exchange.. and it's not a refirb they are sending.. it's the full retail package again I'm going to "forget" to send back the charger and have two.. I never send back the chargers to dell when I do a replacement.. so if they dont ***** about a $100 charger missing they wont ***** about a streak charger missing.. as a matter of fact with my old laptop I forgot to send the charger back and called them, they said "na, it's a minor part. Onky send it back if we contact you abaout it" They never did
But all this time you're doing all this.. you could have a new one on it's way to you with pretty much no questions asked.. just say you got the update.. it said it would reboot.. it rebooted and now youre stuck at the dell screen..
Click to expand...
Click to collapse
but it is worth it we might find better ways of not bricking or having this happen to others
So no luck with QDL tool yet, but I did read about other devices using the method 'Volume Up + Down + plug in USB'
When I tried this my computer recognized an APX device. Will see where this gets me if I can install the propper drivers.
illdill said:
So no luck with QDL tool yet, but I did read about other devices using the method 'Volume Up + Down + plug in USB'
When I tried this my computer recognized an APX device. Will see where this gets me if I can install the propper drivers.
Click to expand...
Click to collapse
i found them but have to find where i stored them or what os i downloaded them in but once you do you can setup the in flash but i am going to tell you know i did it all and the issue i came up wit that made me give up was the bootloader.bin which you will have a hard time finding not unless one of the more talented people here can extract it for you the nvflash wont work properly it uses the the boatloader.bin to reflash the streak but i couldnt find it but i ended up getting my new one from dell after 3 or 4 days
Ok, will wait on your search...
Found a driver that would install as NVIDIA USB Boot-recovery driver. Does that sound right?
I'm also in a bit over my head. From what I understand, I need to restore the boot image on the device. The NVFlash is for flashing the hardware ROM. In what way does/will that help me? Is the hardware ROM part of the boot and system images? Or is it seperate.
Thinking in PC terms, the rom would be the motherboard drivers/software and the System and Boot files would be like installing windows... Does this make sense?
Also, what is the ROM version on the Streak 7?
QDL tool is giving me this error:
ERROR[D10]: no com port found, not in dload mode.
Another question; are the boot, & system files considered "rom's" to NVFlash? Is it a matter of changing the extension to .rom?
OR, like I was assuming earlier, is the rom a totally different file?
Anybody there? I need to understand how this stuff relates to know what to troubleshoot for?
Dear ,
i need help ; i am going crazy with my dell streak 7
i have Dell Streak 7 - T Mobile version
and i have been messing with it ; i put clockwork mod recovery
any how i tried to install the updating yesterday from the dell official update and something went wrong and i am stuck in the clockwork mod ; however i starting messing it more so i chose every wipe in the menu , and after that i i messed more so i formatted everything ( i know that am an idiot by now )
but please i have little bit ignorance in such stuff ; so please can you help me !!!!!!
i tried connecting the device to the laptop win 7 x64 ; it shows me in the device manager that i have android mobile boot mod but again it shows me that i have portable devices ; and also i messed with the sd partition issue .
so i beg u all ; anyone help ..step by step ...am sorry for the trouble
Search and read before posting I made a thread just for this
Sent from my Dell Streak 7 using XDA Premium App
Sir ,,
i swear i read more than 5 websites and i tried everything ...
i just reached to a point that my computer is not identifying the streak as fastboot and when i give the orders to flash it always give wating for device
and when i try to put the dell orginal 3 files on the external sdcard 2 and click back and restore ...nuthing happen as well ...
so please am kind of begginer in such stuff ; can u help
thank you
Read the threads there is a guide and also you cant flash a stock image with a custom recovery ....you need to search on these threads or my threads
Sent from my Dell Streak 7 using XDA Premium App
am sorry sir ,
but i didnt get '' you cant flash a stock image with a custom recovery ....you need to search on these threads or my threads'' you have to excuse my ignorance ...can you explain to me more ..
thank you
That really doesnt matter you need to read the threads some loser just "made" a rom you can flash that might help you
Sent from my Dell Streak 7 using XDA Premium App
am really sorry sir to bother you with my stupidity and my ignorance but please bare with me here ; isnt there a simple way to just flash my strea7 to orginal settings like it was 2.2 and i cant get the old normal fastmode ; note by that my streak is locked on t-mobile and i bought from amazon.com ; and i cant use the 3g cuz of that ; and this is my first time i am using andriod system ..
i tried reading alot of this but still am not getting how to do ; so again am asking is there simple steps 1- 2- 3- ..and flash your streak 7 and get it back like it was ?
sorry for inncovince ..
http://forum.xda-developers.com/showthread.php?t=1006829
Guess I'll just keep talking to myself Anyway, if anyone has some suggestions, feel free to jump in.
So I have to use nvflash in DOS mode, no problem. BUT, (how) can I install the nvidia boot-recovery drivers in DOS mode? Starting to wish I had a linux box.
I managed to answer my earlier question about the ROM and correct me if I am wrong, but the rom is several files packed together INCLUDING the system, boot, etc.
Now is this just a standard zip file? I have my CWM backup, can I zip that and give it a .rom extension?
Hey guys, I realize my situation is bad and that I am a newb, but I did want to thank you all for your help. Without these forums we would all be lost.
Ok guys ... this is the problem ...:crying:
I have (had) a Droid Bionic running ics leak 232 in Brazil (GSM/UMTS ... thanks to xda developers - "bionic in t mobile" thread).
While messing around with the phone connected to linux (baaad idea) at some point I deleted the bootloader ("happy finger" + lack of knowledge os linux).
Now, my phone doesnt power up and RSD Lite doesnt recognize it when connected but, when I connect it to the PC, a green light lits at the top right corner of the phone and Windows recognize it, at the device manager, as a OMAP4430 USB under TI Board tab. This leads me to think that some kind of life still exists down there or, the hardware is alive and waiting for the right software.
After a long quest for a solution, I found this: "forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-gt-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/index9.html".
Now I think this is the way out of this mess (is the same hardware, OMAP platform from Texas Instrument), if exists any, but this was made for Samsung, by Samsung technicians, and doesnt apply to Motorola. :crying: again.
So, is there anyone who can help me, or have any idea of what can be done (other than trow it away or use it as a paper weight)?
Any help would be most appreciated.
Regards
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
its dead
danifunker said:
Have you tried using the command line version of moto-fastboot? It might work, but might not work... I think you need to boot into fastboot mode, but I could be wrong... Either way it's worth a try.
Also, does anything happen when you try to hold down the vol+ and VOL- buttons when powering on the phone?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Thank you for your answer danifunker;
The phone is dead. Pressing buttons does nothing. The only thing that happens is to lit the notification green light at the top right corner of the screen WHEN a plug it in my PC and windows keep telling me this is a unknown device. I unsuccessfully used OMAPFlash, but installing the usb drives that came with it, when I plug it to the PC, windows device manager shows me a new device "OMAP4430 USB" under a new tab "TI Board" , whitch is not recognized by RDS lite or adb or fastboot. Is only recognized by OMAPFlash. If you dont know about OMAPFlash, I found it here http://forum.xda-developers.com/showthread.php?t=1701471 , but this procedure is for a Samsung, witch uses the same platform (OMAP4430), but I dont have the right configurations for the Droid Bionic.
Just the same
chrisp6825 said:
I saw you haven't had any replies yet. My roommate had a similar problem, he managed to mount his system partition automatically and thought his SD card was partitioned into 10 or more partitions.
So he reformated the mount and had a dead phone right after, said he only got a small white light on his notification light when plugged in.
I didn't get a chance to check it out before he took it to Verizon for a refurb, so sadly I'm not much help. Just thought I'd input anything I knew since you still had an empty thread. Hope it comes back alive!
Sent from my kitchen toaster.
Click to expand...
Click to collapse
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
pjcw said:
Thank you for your interest.
If you have any further notice about your roommate problem, please let me know.
And, if you manage to post a reply from your kitche toaster, I am sure you will be able to help in this problem. looking forward for that. :laugh:
Click to expand...
Click to collapse
Can you explain exactly how you deleted the bootloader off of the Bionic? Knowing EXACTLY (what you ran, what you typed) what you did will help us help you.
As an aside, I had no idea there was a SGSII-OMAP variant, but I am not big on the Samsung phones, just assumed they've only been using their own SoCs for a while now...
Hi podspi.
Sorry for the delay.
As a matter of fact, wasnt me that bricked the phone. A friend o mine tryed to flash a gelly beam version, and did it via Fastboot,, under Linux (of witch I know almost notingh).
He told me that the problem was that he made:
fastboot erase mbm
and then
fastboot reboot bootloader
and so the bootloader was lost. He missed a step.
Any help will be greatly aprecieted.
Regards
IOW, since the mbm has been erased, and the mbmflashable hasn't been flashed, there is no way to get it into the bootmenu sceen anymore, right?
Hmmm. Let me ask some other folks too.
Sent from my ASUS Transformer Infinity Running Tapatalk.
I wonder if a factory cable would work to get it to flash mode? Why would you even mess with the bootloader trying to install ICS? You do that through recovery, not fastboot.
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
pjcw said:
I was on ICS ... This was an attempt to get it to JellyBeen ... I, also, dont know why. I was perfectly happy with ICS working in GSM/WCDMA. This is why I am so sad ... It was a very stupid thing to do ... As a matter of fact, I will get a factory cable, but I dont think this is gonna help. Anyways, I am keeping it by side to remember me not to mess with things that are working fine. I'm kind of losing hope that it can fixed.
Regards
Click to expand...
Click to collapse
I think we need to figure out how you flash mbm back onto there. Actually, I think it's mbmloader that you need on there...
mbm = Motorola Boot Manager (?) maybe.
After reading this page: http://omappedia.org/wiki/Bootloader_Project
I believe, mbm = uboot, mbmloader = x-loader
Just found this page... http://www.droid-developers.org/wiki/How_to_load_mbmloader_from_SD_card
download the SBF and grab the mbmloader for ICS. See if you can get a little further...
SamuriHL sHouse of Bionic restored mine when all I could get was fastboot.
Sent from my DROID BIONIC using xda premium
It won't help this. It needs to be flashed at the omap level and since moto isn't about to release the configuration files for the Bionic you can consider this one permanently bricked.
Sent from my Xoom using Tapatalk 2
I tend to agree with SamuriHL. I was thinking that the configuration souldn't be so diferent than others (like Samsung) that uses the same platform (omap). I know that it's naive, but what else could I do. Also, I need the signed files for x-loader and u-boot, of witch I think danifunker is right, this means mbm and mbmloader, that I have, but they came in bin format and not image format (.img). I will try to convert them to .img, but I am at the end of my resources (not that they are so many), and will give up shortly. At this point (giving up), I will buy another cellphone AND IT WONT BE A MOTOROLA, Probably a HTC or a Samsung. But I will keep Bionic at my desktop, as a paperweight, to remind me how I liked it, how I mess things up.
Anyways, if I manage to solve this problem, I will post here, and I wish to thank everyone that spare their time to try to help people. If anyone have any suggestion, I'll be glad to follow.
If you modify them in any way they'll no longer be signed and won't work. Someone else already went through several weeks of trying to fix their phone that had similar issues. He's well connected and still couldn't get the necessary files. Don't necessarily give up on Moto, though...it's not their fault we're stuck with locked bootloaders. Blame VZW for that one. Even Samsung was forced to lock the S3 on VZW. Things may change some day. We'll have to wait and see.
You can always get RAZR i with the unlockable bootloader! that might make things a bit easier...
IT'S DONE!!!!!!!!!
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
SamuriHL said:
Holy.....uh, well, WOW! I'm in awe here on this one. WELL DONE!!!!!!!
Click to expand...
Click to collapse
Can we use this method to flash any firmware to the phone? Lets say you load the latest ICS, maybe we use this method which restores the most original bootloader to the phone and then flash to any version?
Which version did you fastboot to?
pjcw said:
IT'S DONE ....... IT IS ALIVE AGAIN :highfive:
Guys. My phone is alive again. Thanks to FRAGULINA and PICGRABBER for their unvaluable help. It is now running GSM with data enabled (3G) with ICS 232, rooted, thanks to FRAGULINA and HTCFlyerX ( http://forum.xda-developers.com/showthread.php?p=31101192&highlight=build+prop#post31101192).
Well, I'm attaching 2 zip files. One is omapflash and the other is "THE FILES", and instructions on the "release_notes.txt". This works on LINUX.
And works like a charm. Took me (much) less than 5 minutes to get me from a dead phone to bootloader fastboot. And the rest is history. Well known procedures.
Thanks to all of you that helped or tryed to help.
Enjoy.
To those who have an interest in new challanges (as I know you are), i'm opening a new quest and would appreciate your thoughts.
I have at hand an atrix 2 and I want to find where in hell is the subsidy code writen at and how can I read it. This new quest will be at the proper location at the atrix 2 forum.
I think we won this challange. Lets go for another.
Any doubts I am available to help.
Regards.
Click to expand...
Click to collapse
This is unbelievable. After talking with you on Gtalk, I thought this was a permanent brick. Thanks for the files...I have a guy on gtalk right now who can benefit from these.
Ok so I purchased an i9000M that was advertised as broken (got it for cheap) to see if I could get it going for my step daughter. I turn it on.... I get the samsung boot screen and goes black when it should be booting OS.
Windows still recognizes it somewhat. If I look in device manager under "portable devices" It shows a "j" and "k" drive that are identified as i9000 and i9000 sd or something like that. Although Windows sees it.... It wont mount these drives unfortunately.
Things I've tried ( Before someone suggests I use a JIG............. It doesn't and will not work on this phone)
USB JIG (tested and working on my Hercules)
SD Card Partition (EXT4 and FAT32) because I suspect borked internal storage
SD Card Partition (ReiserFS and FAT32) Still nothing......... then I realized the phone probably wasnt rooted
3 button combos ( every single combination) nada
plugging in USB cable while holding volume up and down...
ADB Reboot recovery/download ( not recognized because I cant turn on debugging)
ETC ETC ETC........
I have been searching google for hours for some kind of clue as to what can be done other than JTAG repair and All I come up with (no matter what site im on) is " Use a USB JIG" duhhhh Its getting rather annoying.
Im no stranger to flashing ( no expert) but this one has me stumped. I was considering buying a RIFFbox anyways but I thought maybe some experienced users out there might be able to suggest something.
My hope is that something can be done with the J and K drive that was mentioned. Perhaps I can format and somehow push a rom straight to the internal storage without any assistance from the phone itself...... I know..... wishful thinking. or perhaps boot straight from external SD???? That would be interesting!
More to this.... I realize this question has probably been asked a million times because it seems to be a common issue on this phone but I suppose my long winded question really boils down to my last paragraph which I havent seen suggested yet.
EDIT: I have a Windows 7 AND kubuntu 12.04 dual boot if any suggestions require linux
Any help would be greatly appriciated.
kibosh1981 said:
Any help would be greatly appriciated.
Click to expand...
Click to collapse
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
xsenman said:
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
Click to expand...
Click to collapse
Thanks. i will have a look and experiment tomorrow.
I'll report back my progress
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
taz0697 said:
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
Click to expand...
Click to collapse
As I mentioned.... no download mode, therefore.... No ODIN. Unless someone has some magical way to make it work otherwise. The computer knows its an I9000 at least. Kies says its in the wrong mode and I have no UI so debugging is out of the question.
Also: Xsenmen. I was unable to get any of the tools to connect. In one section you mention that AndroPlatina attempts to connect while booting? I was unable to get this to happen. I even tried the "heat trick" to no avail
Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie
Sorry - one other question!
Which key is the "enter button"?
FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.
Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!
Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.
Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.
I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect
And that's on the charger it came with?
It's not looking good.
FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse
julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks
It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?
I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.
FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548
Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one