Related
Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.
Hey everyone ^^
Hoping I can find some help here, else it'll be another phone consumed by the bricking plague
I recently tried to flash the latest CM from sourceforge, but the flashing process was interrupted (Powercut FFS). So the phone's stuck at the bootscreen. Normally, it'd be a case of rebooting into download mode and retrying, but....
My home key is buggered, it had a disagreement with some rain. Again, normally it'd be fine. Just use ADB to get into recovery/download, but...
The bad flash has made the phone unable to be recognized. Unsure whether it fails before it initializes USB, but it just won't be picked up on either ADB or Odin.
It's not all bad, I can still see the first Galaxy S bootscreen (The first one being the static, unflashey one).
TL;DR: Phone is buggered, unable to use "conventional" methods to access download mode, bootloader is still intact.
Could somebody please give some advice on this situation? It'd really help me out! Not keen on getting a new phone just yet
Cheers,
Morgan ^^
use JIG mate
http://forum.xda-developers.com/showthread.php?t=819551
thanks to TheBeano.
Yeah, I was looking into that. Unfortunately it'd take a few weeks for the parts to get here (No places like RadioShack etc) and this phone needs to be working ASAP (Usual story, right? ). Short of taking a knife to the AC adapter and hoping that I can find a 300K resistor, I'm at a loss as to what to do...
And now, this is even more interesting. Out of curiosity I decided to try to install my phone's drivers manually (For some reason Windows wasn't picking them up). The ADB drivers installed without any problems and I can now issue commands via ADB
The bad news is, well... Apparently most of the system stuff is missing. No /System/Bin directory at all (The only thing in /System is Lost+Found). Which, obviously, is bad. I tried issuing "reboot recovery" and "reboot download" which both worked, except the phone quickly flashed a white/blue line across the screen and restarted.
Is there any way to restore functionality through ADB? Can I push files to the /System/Bin directory (And all other missing things...)? If so, where would I get the files?
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
Hello all,
I am very new to the community of rooting and am completely lost. A friend of mine gave me this dell streak 7 because someone gave it to him and he was never able to get it to work. I am stuck at "Starting Fastboot USB download protocol" If someone would possibly explain how I might go about fixing this and using it with it's maximum potential I would appreciate it very much. Now although I am very tech savvy I don't have the slightest clue about rooting or loading custom roms so I will have to be talked to like a child until I get comfortable. As of now I have connected the streak to my computer but have yet to have it recognized. That's pretty much as far as I have gotten. I do have a 32gb SD card as well if it needs to be used in the process somehow.
Thanks for all everyone's time and help
Incase the thumbnail does't work here is a link for dropbox
dropbox.com/s/yqc8s4ndybqrwnr/2013-02-25%2009.08.52.jpg
Your not stuck, it's just waiting for you to use the Fastboot command from your PC. Open the little side door, insert a small paperclip into the small hole to reboot normally if it will.
Read this also: http://forum.xda-developers.com/showthread.php?t=1395964
YAY !
wptski said:
Your not stuck, it's just waiting for you to use the Fastboot command from your PC. Open the little side door, insert a small paperclip into the small hole to reboot normally if it will.
Read this also: http://forum.xda-developers.com/showthread.php?t=1395964
Click to expand...
Click to collapse
ok so, while waiting for a response from someone on here I was playing around with it and realized that the first step i was missing was getting the computer to recognize the tablet. I never had the correct drivers installed and I was having a hard time getting windows to recognize the drivers.
Anyway I am finally able to get the drivers into windows and now I am able to control the device from the command prompt on the computer.
What is my next step? how do i load the rom into the device ? and which one is the best to use for this one ?
I'm thinking the last person who had this device messed it up very badly and now all it wants to do is go into fasboot mode nothing else, i thought I had installed the (Clockwork mod recovery.img) S7-6.0.1.2.img into the recovery using this guide http://forum.xda-developers.com/showthread.php?t=1334487,
After i do that I says done. but nothing happens on the device after is says "Flashing StorMgr partition recovery"
sending 'recovery' (4742 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.010s]
finished. total time: 0.543s
ddg5060 said:
ok so, while waiting for a response from someone on here I was playing around with it and realized that the first step i was missing was getting the computer to recognize the tablet. I never had the correct drivers installed and I was having a hard time getting windows to recognize the drivers.
Anyway I am finally able to get the drivers into windows and now I am able to control the device from the command prompt on the computer.
What is my next step? how do i load the rom into the device ? and which one is the best to use for this one ?
Click to expand...
Click to collapse
You have your choice. You can use HoneyStreak ROM's by DJ_Steve, which are completed (Honeycomb Android 3.2)
You can run my CM10.1 (Android 4.2.1)
Where to now ?
giveen said:
You have your choice. You can use HoneyStreak ROM's by DJ_Steve, which are completed (Honeycomb Android 3.2)
You can run my CM10.1 (Android 4.2.1)
Click to expand...
Click to collapse
Yes but exactly how do I do that? I can't seem to figure out where to start the flashing process. All I am able to do with my device is get into fasboot mode, where do I go from there ? I want to use CM10.1
I tried holding vol (+) and power - nothing
I tried holding vol (-) and power - nothing
Thanks again for all your help
Search is your greatest ally. This has been answered a good 50-100 times.
Yes i know
giveen said:
Search is your greatest ally. This has been answered a good 50-100 times.
Click to expand...
Click to collapse
Yes I realize this but as I am extremely new to the scene and there is sooooo much info, it's hard to know where to begin. I don't even know what to look for really because I don't know what tools do what. It's like having all the pieces to the puzzle but unable to put them in the correct order.
ddg5060 said:
Yes I realize this but as I am extremely new to the scene and there is sooooo much info, it's hard to know where to begin. I don't even know what to look for really because I don't know what tools do what. It's like having all the pieces to the puzzle but unable to put them in the correct order.
Click to expand...
Click to collapse
Basics of flashing: http://www.youtube.com/playlist?list=PLB99FAE280F618B12
Please help?!?!
wptski said:
Basics of flashing:
Thank you. I will look at these and hopefully it will clear some things up. The problem is that my situation is unique I think. I don't know if maybe i have a broken button or the person who gave it to me really messed it up but all it does is boot into fastboot automatically, although I can get it into NVFLASH mode i don't know what these modes do. Are they both able to flash the system so I can use the device? If so do some files work in one that don't work in the other?
I tried putting the device in NVFlash mode caus I want to put the CM10.1 FW on it, am I headed in the right direction ? The only things that I can launch are "Install JB_Alpha_E.bat" and "NVFLASH.exe" running the Install_JB one opens the command prompt and it looks like it is doing something which is how it looks in the video but then suddenly after it processes some files the command prompt window just closes, am I doing something wrong ?
Click to expand...
Click to collapse
You are doing it wrong. Go read my first post in that thread very very very very very very very carefullly.
http://forum.xda-developers.com/showthread.php?t=2130081
I'll give you a hint, the line you want to pay attention to is stated right above the download links.
Failed executing command 12 NvError 0x12002
So because the cmd prompt closes so fast I cannot see the error, so I took a video and paused i played it until it froze right where the message came up.
Here is what it says if failes right after creating partitions blah blah blah
Failed executing command 12 NvError 0x12002
command failure: create failed (Bad data)
bootloader status: fatal failure to read / write to mass storage (code:9) message: nverror:0x8 (0x19000008) flags: 0
What does that even mean ? is the device broken somehow ?
Sorry
giveen said:
You are doing it wrong. Go read my first post in that thread very very very very very very very carefullly.
http://forum.xda-developers.com/showthread.php?t=2130081
I'll give you a hint, the line you want to pay attention to is stated right above the download links.
Click to expand...
Click to collapse
Sorry I seem so dense when it comes to this stuff, I really don't know android stuff that well.
I looked back and maybe I'm missing what you are saying but I already have the device in NV mode and have the drivers installed if that is what you were talking about.
Now it's just the crashing problem that i'm having. Any ideas? or am I still doing it wrong?
ddg5060 said:
Sorry I seem so dense when it comes to this stuff, I really don't know android stuff that well.
I looked back and maybe I'm missing what you are saying but I already have the device in NV mode and have the drivers installed if that is what you were talking about.
Now it's just the crashing problem that i'm having. Any ideas? or am I still doing it wrong?
Click to expand...
Click to collapse
Sorry, at the time I had posted that you were still working with fastboot.
Do you have the drivers installed and in device manager it states that it sees "nvidia recovery" ?
Hard reset with a push pin, go back into NVFLASH mode again, and run the batch file again. If it fails, you hvae to do this step every time.
giveen said:
Sorry, at the time I had posted that you were still working with fastboot.
Do you have the drivers installed and in device manager it states that it sees "nvidia recovery" ?
Hard reset with a push pin, go back into NVFLASH mode again, and run the batch file again. If it fails, you hvae to do this step every time.
Click to expand...
Click to collapse
Yes I am in NVflash mode, I have done the pin press and retried several times each time it the cmd closes and i assume it is getting that error.
i can post a picture of the freeze frame that i was able to pause it on if that helps.
ddg5060 said:
Yes I am in NVflash mode, I have done the pin press and retried several times each time it the cmd closes and i assume it is getting that error.
i can post a picture of the freeze frame that i was able to pause it on if that helps.
Click to expand...
Click to collapse
I forgot to mention that I did also install the drivers using the nvidia package like the tutorials stated. That all went fine.
Ps. Ignore the play button the the picture, it's just a screen cap of my phone paused on the frame.
ddg5060 said:
I forgot to mention that I did also install the drivers using the nvidia package like the tutorials stated. That all went fine.
Ps. Ignore the play button the the picture, it's just a screen cap of my phone paused on the frame.
Click to expand...
Click to collapse
Your SOL.
Notice it says FAIL TO READ/WRITE
You are in read-only mode.
giveen said:
Your SOL.
Notice it says FAIL TO READ/WRITE
You are in read-only mode.
Click to expand...
Click to collapse
Ok, i did notice that, other than the obvious what does that mean, is it possible to get it out of read only mode?
ddg5060 said:
Ok, i did notice that, other than the obvious what does that mean, is it possible to get it out of read only mode?
Click to expand...
Click to collapse
Only one user has claimed to have gotten out it without returning it to Dell.
wptski said:
Only one user has claimed to have gotten out it without returning it to Dell.
Click to expand...
Click to collapse
Damn, let me guess, he won't tell anyone how to do it either or show pictures of claimed revived device.
As far as dell goes, is it something that they will fix or do they consider the warranty void because of whatever was done to it to make it like that?
So sad and here I thought I was actually progressing in fixing it. Question though, how does something like that happen? Did the person flash it wrong? Or interrupt it while writing some critical process?
Actually he did tell us how to do it, it was just 1 in a million chance it works.
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