Related
hi there.
ive bought a refurbed hero from "3" uk, however it doesn't boot. it wont go into recovery either (home+pwr).
it will go into the fastboot though (pwr+back).
the phone connects to the pc, and the pc finds the phone using "fastboot devices" and "adb devices".
i tried flashing a custom RA recovery, however i received the message "failed remote not allow".
googling it, i found out it is because of the hboot being 1.76....... which needs flashrec to install a custom recovery. problem is i cant boot the phone to use flashrec.
basically is the phone screwed?
ive called 3 and they are sending a replacement on monday. i will then have to send the old one back to them myself, meaning ive got a few days to make sure the new one works etc, check condition.
thing is the one i have now is perfect and new looking. i could receive a slightly damaged working one on monday, so i want to see if there is anything i can do to fix it.
thanks for any help
What happens when you try to boot up normally? ... Anything?
How about without the SD in?... Does it make a difference?
when i boot up normally, it displays a thin "hero" logo, then after a while displays a htc logo with a green alien popping out.
a minute after that, it starts all over again until the battery is pulled.
tried with and without an sdcard, and no difference.
Flash a new official rru from HTC. If you can't do that you should be able to create a goldcard and flash a the rru that way. Check out parts of my guide and make up the rest.
i just got it sorted.
i downloaded the ruu, tried it while in fastboot mode. it didnt work, so i looked through your goldcard thread, and realised i hadnt got adb setup 100% (device manager had it down as android device or something, so did as instructed in the thread).
connected it up to the pc while in fastboot mode, then ran the ruu. it worked this time!
thanks alot for the help. its saved me alot of hassle sending the phone back.
Hi guys
Let me start off by saying..I should have never attempted this myself.
I'm hoping somebody could please help me with my somewhat-bricked device..bricked in the sense that I don't know what to do with it. (i'm a noob to this). I've tried installing a custom rom and completely screwed up my dell streak 5.
So the phone doesn't boot anymore and just takes me to the option to install update.pkg off the sd card. I added the file along with recovery.img to the sd card.
360 17397 00 May 31, 2011 PKG Recovery Hash Latest Retail rom
My problem is that I cannot for whatever reason get Flashboot to work in order to flash the recovery.img first. under device manager you see android phone/android adb interface but still can't manage the connection to use cmd prompt/fastboot.
Is there any other way of getting the recovery.img to work without fastboot..maybe thru the sd card. I have no idea what i'm doing anymore. I've tried installing the update.pkg but after installation it just stays on the dell logo loading screen forever.
PLEASE help if you can.
Well lets start off to get you back on a stock rom, as it sounds like that would be the easiest at this point. We can move on to a custom rom from there.
The pkg file you downloaded....did you rename it update.pkg ?
If not, rename it update.pkg and make sure it is on the root of your sd card. Get to the recovery menu where you have the option of upgrading from update.pkg and choose it. In about 5 minutes, you'll have a clean stock rom.
I tried installing the 360 rom listed on http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
I did name it update.pkg
It went through the installation phase but on reboot it doesn't get past the Dell Logo loading screen. Any suggestions?
On the screen where you choose upgrade from update.pkg, choose factory reset and see if that helps
Tried both..unfortunately, same end.
Is flashing recovery a required step prior to doing this..because I was unable to do that.
Also, Thank you for taking an interest. I really appreciate it.
yes, you need to have the recovery for the rom you are flashing (at least when it comes to stock roms). My understanding is that the pkg file is encrypted and the recovery decrypts it.
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/suppor...dateid=-1&formatid=-1&source=-1&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/showthread.php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
Once that is done type in the following command: fastboot.exe reboot
Get ready to hold down the Volume + and - as soon as the screen goes black.
Now choose Upgrade from update.pkg
It should work now. If not, someone else may have to help you with another method such as QDL tool. I've never had to use that.
This is a screenshot of the problem i keep running into. i installed the drivers just as you said and am at the step with fastboot.
imgur [dot] com/gw2A0
Any advice? Thanks again
im an idiot.
i got fastboot to run and send over the recovery.img
currently installing the update.pkg but its still stuck at the Dell Logo screen upon reboot. No idea what is going on.
FIXED. You're a miracle worker. Thank you so much.
Only problem I have now is an irritating sequence of flashing buttons every now and then. Have you had a similar issue in the past?
THANK YOU so much again!
Are you on a stock rom still? Or have you moved on to a custom rom? Typically the flashing led's happen when you are running a rom with an "incompatible" baseband, but that should be pretty near impossible if you are running a rom installed from an update.pkg rather than an update.zip.
running the update pkg off the wiki site.
Only other problem I've noticed is that I can't get it to root. I've tried gingerbreak and superoneclick..both of which worked flawlessly in the past.
Baseband GAUSB1A134700-US
KERNEL 2.6.32.9-PERF
BUILD 17397
I really want another crack at getting streakdroid, but the phone just isn't budging. Tempted to flash/install another rom but worried as heck that this same incident is going to come up. (the flashing lights started after i updated the AMSS and DSP last night--my first attempt at installing streakdroid 2.3).
Installing the stock rom via the update.pkg file will overwrite the amss and dsp1. That's the biggest difference to the end user on update.pkg vs update.zip. It's the actual recommended way to install a baseband. There are several firmwares, besides amss and dsp1, that get installed with a pkg.
Now that you have MultiRecoveryFlasher on your pc, installed StreakMod (custom recovery) should be a breeze for you. The only thing to watch out for is since you have a stock rom now, the first time it boots it will rewrite the recovery back to stock. Here is how to get around this:
Download the custom rom of your choice.
Place the zip file on the root of your sd card.
Get your phone back in fastboot mode
Using MultiRecoveryFlasher, flash StreakMod
As soon as the screen goes black for the reboot, hold the volume +/- keys.
Choose option 2 again, this time it should take you into StreakMod
Choose flash from update.zip
On the next screen, choose search for zip file (similar wording)
Choose the custom rom from earlier
Let it do it's thing.
Choose reboot system now
Again, as soon as the screen goes dark, hold Volume +/-
Now choose option 1 - Factory Rest
Let it do it's thing.
It should boot up now and your custom recovery will stay intact.
Let me give you some friendly advice: Streakdroid 2.3 is too much of a work in progress. Install one of the other Streakdroids, Longhorn, Simple Streak, or even my Streakin' 354. Play with it for a while and learn a little more before jumping into one that may not be as stable.
As far as rooting a stock rom, the preferred method is via superuser.zip. I'm not at home, so I don't have the file to upload for you, but its on these Dell Streak forums somewhere. You have to have a custom recovery to use it though. The custom roms are all rooted already.
Thank you for everything
No problem. Did you get it working?
Sent from my Dell Streak using xda premium
Absolutely and I couldn't have done it without you. If you had written out just one of the x number of tutorials out there, I don't think anyone would have run into the problems I did at first.
Streakdroid 191 runs like a charm---snappy and more responsive than stock ever was.
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
lordmorphous said:
Glad to hear it...I was lost when I first started too. Someone helped me out and I just like to pay it forward. It's what makes this forum my favorite.
Click to expand...
Click to collapse
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
dwadetiu said:
Hi guys.. Hi Mr Lordmorphous.. im a super noobie in dell streak 5.. i got my dell streak a month ago.. today my phone doesnt work.. im stuck on Dell logo when i am going to switch it to on.. i really dont know where to start and how to type the codes like you are talking about like .pkg ing. etc. .. when im pressing the factory reset nothing happens.. i also tried to click software upgrade via update.pkg on SD card and nothing happens .. i clicked also the screen calibration it says *successful calibration done*.. im totally lost.. can u help me how to start from beginning (like for super noobie like me)? also the codes that im going to type in pc.. thanks in advance!
Click to expand...
Click to collapse
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Hi again guys.. and mr lordmorphous!
im following what you told him (aaivazi)..
I'm going to try to start from scratch here. I am also assuming you are using a Windows PC.
Download the drivers from Dell. Here's the link:
http://support.euro.dell.com/support...&fileid=433681
Install them and reboot your pc.
Download MultiRecoveryFlasher from here:
http://forum.xda-developers.com/show....php?t=1000455
Extract it to somewhere on you pc where you can find it.
Now this hasn't been updated to include 360's recovery, but that's ok. We don't have to run the utility. It's the support files that are included that we are going to use.
Download the recovery.img for 360 (which I think you have already done)
Put the recovery.img in the root folder of MultiRecoveryFlasher. There should be other files in there such as fastboot.exe, adb.exe, etc.
Power down your phone and restart it in fastboot mode (hold down camera and power button together until you get a white screen. When fastboot appears in upper right, select it and plug your phone into your pc)
Verify the phone displays fastboot ready
Open a command prompt on your PC
Type in the following command: fastboot.exe -i 0x413c flash recovery recovery.img
(im already here but this is what the command prompt says:
'fastboot.exe' is not recognized as an internal or external command, operable program or batch file.)
what should i do ?
Streak4ever said:
RTFM
http://forum.xda-developers.com/wiki/index.php?title=Dell_Streak
Click to expand...
Click to collapse
hi streak4ever thanks for reply.. what does RTFM means? thanks
Hi Guys,
I am a noob to xda so please bear with me...
Hoping someone can help me out here.. I will try and explain in as much detail as possible and provide you with as much Info from my phone as I can.
Firstly my phones details
Motorola Atrix 4g (UK version) Second phone as busted the last one. Bought outright as a retail sale.
Orange UK
System Version: 45.31.0.MB860.Retail.en.GB
Android Version: 2.3.4 (After UK released update)
Baseband Version: N_01.100.00R
Webtop Version: WT-1.2.0.133_38
Kernel Version: 2.66.32.9 [email protected]#2
Ok so, decided to root my phone. To do so I used petesMotorolaRootTools_V1.07 found on the website psouza4.com/bionic/
This worked fine and an app installed from the App Market confirmed that the phone was Rooted and had Superuser permissions.
Next I downloaded ClockWorkMod Rom Manager from the Market Inc Premium, SetCPU, Rom Toolbox & Titanium Backup Free. I had a quick look at these apps once downloaded but didnt really do a lot,
However, when Rom Manager opened it promted me to Flash ClockWorkMod Recovery, Which I did and then selected Back up current Rom. I also did this, (bear with me it gets a little vague here as to what I remember seeing)
Now I'm sure it said something like Nandroid Backup, which I selected. It proceeded to say something along the lines of, Backing up or phone will now reboot??
Anyhow, what ever it said, it started to reboot. The Motorola Red Circle logo came up but then at the top it said reboot failed and something ilse that didnt make sense then froze. I pulled the battery and rebooted. Seemed to work fine. Maybe a touch laggy but nothing to bad.
Next did my research into what ROM I'm likely to want to try. Found a few but seemed from what I have read on various forums that they dont work well for uk phones. Then decided perhaps then flashing should be left alone and went back to PetesMotorolaTools and unrooted. before I unrooted however i removed all apps that required root access first. Possibly a mistake?
I noticed that a few preinstalled apps werent working, nothing important or anything I use but there icons were like Blue settings icons all the same.
Did a factory reset through the handset also, in an attempt to return to factory settings.. not much changed really. Also tried to update software though the Motorola website but it said I was all up to date.
I thought maybe that something went wrong so I rooted again. This time the unroot failed. I then dowloaded all the rooted apps that I had before and then unrooted. This worked. Not sure if coincedence or not but it worked and when unrooting it said unfreezing apps about 6 times, before the complete message. Then uninstalled the root apps again.
Most, not all but most of those preinstalled apps were then working ok.
I read a little bit more bout Roms and decided to have another bash. Found and downloaded a few to comp. Then I place an SD card into phone and Flashed it. then tranferred a copy to its root.
Rooted the phone in the same way as before. Downloaded all the apps again opened CWM RM, Flashed CWM Recovery again as was unsure that the time I did it before would work. Then selected back up Current ROM. Without any message this time the phone started to reboot.
It came up with the recovery screen (Android man and !) From what I have read the next step is to tap the bottom right of the screen to bring up the menu.
This did not work nor did anything else happen. After waiting about 25mins with nothing more happening I pulled the batt again.
Decided I'd boot into recovery mode manually and see if the bottom right of screen would work that way. turned off then held On and down Vol. Fastboot showed at top, Scrolled and selected Android recovery. Same Android Man and ! came up, tried tapping the bottom right of screen again.... It didnt work.
Read more on the forums where someone said that pushing up and down on the Vol buttons works. Tried this and hey presto.. a new menu appears. Shown as follows.
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
No back up options so rebooted....
Anyway thought I'd try a few times to use CWM RM to flash a rom to device. Each time it took me throught this same process.
Eventually I though what the hec just try and flash it...
So I selected the apply update from sdcard option.
Then selected the ROM I saved to SD Card.
Then the following text appears on screen in yellow.
--Install /sdcard...
finding update package...
Openeing update package...
Verifying update package...
E:signature verification failed
Installation abborted
I tried this a few times to no avail. even tried downloading the roms from CWM RM with no change.
Read some more on the forums and somewhere read to rename the ROM update.zip
Did this and tried again.... No Joy!!!
Selected Fix permissions in an attempt to clean up and thats as far as I have got...
I'm at the end of my tether and dont know what to do...
Please, please, please someone help me get to the bottom of my dilemma..
Thanks for reading and any help in advance.
Just a little more info to help diagnose
CWM RM Details
Rom Manager Premium v4.8.1.3
Current Recovery: ClockworkMod 5.0.2.0
Latest Recover;ClockworkMod 5.0.2.0
Thanks again peoples for taking the time to at least read this..
No where in there did I see "I unlocked my bootloader"
That's fine that you're rooted, but to use CWM Recovery, install ROMs, make Nandroid Backups, etc. you need to unlock your bootloader first! See the international part of the Pudding thread (since your in UK) in the dev section.
Sent from my CM7 Atrix 4G
Ah Hah! You are correct at no point did I unlock my Booty, Thank you I shall give that a go and report back...
Ok so, I have trawled the forum and many others this avo on my research quest to unlock the bootloader as advised above but have been unsucessful so far.
I used the Pudding thread as you said.
when downloading the files advised I noticed that some were downloading as unrecognised files. I still proceeded to follow instructions as written.
Some of them like the RSD Lite I managed to unzip and extract with a programme I have however the next one needed said it was Undefined File type.
Anyway I deleted those files and tried following the other method listed underneath the driver via the link at "Guide for beginners provided by..."
This was unsucessfull as the "fastboot oem unlock" command was not recognised.
Pulled the batt and rebooted into normal mode and I'm back at SQ1
Bit stuck if anyone has any ideas..
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Dcskeete said:
Thank you for your explanation... I will give it a go when I get back from work tomorrow...
I appreciate you taking the time to help..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You should definatly also install busybox
Swiftks said:
Ok, here goes...
1) Make sure you have the drivers installed on your computer. (Available in Pudding Thread)
2) Go to pudding thread, and grab the Unlock Only IHOP sbf file (assuming your not on AT&T).
http://forum.xda-developers.com/showthread.php?t=1136261
"Unlock:
Unlocker only SBFs - These small 1mb SBF files will get your phone ready to fasboot oem unlock. They are the files most people should use.
ATT ONLY - Unlocker for 1.8.3 and 4.5.91 ATT firmwares
Orange/Bell/Telestra/Latin America/International users ONLY - Download IHOP"
3) Download & install RSD Lite. (Available in Pudding Thread)
4) Put phone in RSD Protocol Mode.
a) Power off phone
b) Upon Powering ON, hold Power Button + Volume UP
5) Connect Phone to computer via USB
6) unzip the IHOP sbf file to root of your C:\, open RSD Lite program, and drag sbf file onto File Name Box. Make sure RSD Lite sees your device connected to it, and then flash away.
7) After the sbf has flashed (hopefully without any errors), reboot your phone into fastboot mode (Power Button + Volume Down; when you see fastboot, press volume up to enter fastboot mode).
8) Re-connect phone to computer if you disconnected it.
9) In the folder where your fastboot files are located (if you don't have fastboot files, go download them from sticky in General Section), press Shift + Right Click, select Open Command Window Here.
10) With phone in fastboot mode, connected to PC and command window open in fastboot file location, type:
fastboot oem unlock
*This will give you your device #
Then type:
fastboot oem unlock [insert your # here]
10) Bootloader should unlock, then type fastboot reboot to reboot the phone. Should say Unlocked on boot screen now, if all went well.
11) Install Rom Racer's Recovery or Rom Manager, and you're good to go.
Think that about cover it... if you have any problems, give details of what is happening and at what step. Also, check the Pudding thread for possible solutions, as most problems have already been solved there.
Click to expand...
Click to collapse
A BIG THANKS!!!
Thanks so much for the advice and instructions... Unlocked beautifully... Now to find the ideal ROM....
Dont suppose there are any suggestions for International (UK) Atrix users??
Really appriciate the help..
Regards
Danny
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Im not sure, maybe someone else can confirm. You should be using moto-fastboot to unlock & not regular fastboot, right?
Sent from my MB860 using xda premium
draken_1337 said:
I would recommend that you flashed TWRP 2.0 through CWM direct link. It lets you have touch screen in recovery; much easier! Then if you like CM7 you could try this or if you like the MIUI style (like me!) you would want to try this! It hasn't in-game audio yet but it's much cooler in my opinion. But Neutrino CM7 is really great!
Click to expand...
Click to collapse
People have had problems with TWRP.............stick with Romracers CWM, it's tried and trusted. If the touch screen in CWM gets you off, so be it, but I'd rather have a recovery that works with all ROM's, and not just some.
I went to update to KitKat and it was nearly done and then the "No Command" error came up. My tablet has an unlocked boot loader but isn't rooted. However it was before but I updated it from an OTA and that got rid of it. I've tried booting into recovery etc but the same thing happens.
Anyone have any advice please?
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
tgearhar said:
Same exact issue and set up here. Also, maybe I'm just dumb, but I can't get my tablet to turn off either. It just keeps cycling back to the "no command" screen until I do something.
Click to expand...
Click to collapse
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
gunner1937 said:
I think that both of you what you see (the "no command") is your stock recovery, if indeed you see an android with a yellow !.
If it is the case to access the menu of the stock recovery press power and tap volume up. The menu will give you the choice of rebooting your Nexus 7.
Click to expand...
Click to collapse
I can get to the menu but when trying the reboot option, it just cycles the same way again. Back to the android with a red ! and says "No command." I also tried clearing cache and data to no avail. I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
I spent too much time messing around with and learning how to do things with my SIII and not enough time with this
Same deal here! Not sure what to do short of wiping and losing my info.
Same here...any advice? Not sure what happened. OTA update too.
Significa said:
Same here...any advice? Not sure what happened. OTA update too.
Click to expand...
Click to collapse
Wow, this seems to be widespread, at least somewhat. I'm in same situation. Toolkits, adb, nothing works. I thought this was a soft brick, but now I'm thinking it's toast. Probably doesn't help that I didn't have Dev options enabled along with USB Debugging. I can't even turn it off. Just bootloops after Google logo shows up twice, then to No Command error, then starts over again. I wonder what the hell is causing this. (Device was locked and unrooted)
Same boat here, even sideloaded the factory image via ADB.
[QUOTE [/QUOTE]
I was going to try using ADB to manually push the update but my computer was recently updated and now I can't get the driver installed for some reason.
If you have android-sdk-windows installed on your computer do not forget to update it through "SDK Manager.exe".
Pushing via ADB didn't work for me. That also failed.
I caved and called Google. Tech support is stumped as well.
Sent from my Nexus 5 using Tapatalk
Could this be a widespread issue? Like I don't even understand why it happened at all!
Sent from my Nexus 5 using XDA Premium 4 mobile app
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
My wife's 2012 N7 is having this same problem. Unlocked bootloader, but I reflashed factory image and unrooted before giving it to her. She got the OTA last night, and now stuck at No Command.
I've subscribed to this thread, hoping that you guys will have it solved before I get home from work tonight! Would love to not have her lose all her data.
(I was kinda mad that she got the OTA last night and I haven't got it yet on my 2013 N7, but that's another gripe for another thread)
killswitch11 said:
Two things: That guide says you must have USB Debugging enabled. Since my wife had this tablet, I did not have dev options enabled at all, including USB debug.
The other thing is that when I run the SDK Manager, nothing happens on my computer. I double click it or try Run as Admin, and a small CMD box flashes on my screen for a millesecond and disappears. That's all.
Click to expand...
Click to collapse
Unfortunately I'm not sure on the SDK manager part. As far as the USB Debugging, I'm 98% sure that I did not have it enabled either. I think I did at one point but after doing several OTA upgrades, I'm sure it got unchecked.
---------- Post added at 01:34 PM ---------- Previous post was at 01:01 PM ----------
kr33mo said:
I ended up doing and it worked for me as well. Wiped everything though. How can I restore / reinstall my apps w/o needing to download them all again?
Click to expand...
Click to collapse
I don't believe there is a way. Maybe someone smarter than myself can chime in but I had to let the play store do it's thing and re-download all of mine.
tgearhar said:
I finally got mine working again!
I tried a million different things so I'm going to try and explain my process as simple as I can, I apologize in advance because I am far from an expert...
First, I tried using the method, well some of it, from this thread: http://forum.xda-developers.com/showthread.php?t=1907796
- I would suggest using this thread to get everything set up (drivers, ADB, the factory image downloaded and in the correct file location) I wasn't able to get the drivers working correctly with that route so I ended up using the toolkit to get them working but that thread helped me get all of the system files in the correct location and helped get all of the ADB stuff set up.
Once you have everything set up and your computer recognizes the tablet, (I checked that by opening a cmd prompt and using the command from the original thread above "adb devices"). As long as you see your device, I think you should be good.
From the "No Command" screen I held down Power and Volume + to get the menu to come up. I then chose the Restart option and immediately held Power and Volume -. This got me into the Fastboot Mode.
Once in Fastboot mode I went to the cmd prompt on my computer and used the following commands in this order from this post:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
*Make sure that all of the image files are in the proper location on your computer otherwise this step is worthless
The tablet then rebooted normally and I was able to set everything up again. Again, I am by no means an expert at all, this is just what worked for me. Try at your own risk.
I hope I covered all of the steps, I tried a million different things last night so they all kind of run together.
Click to expand...
Click to collapse
Worked for me! Thanks, I don't believe I had USB Debugging enabled either. Shame it wiped all my data though.
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
Click to expand...
Click to collapse
Worked for me as well. Really appreciate that.
Sent from my Nexus 5 using Tapatalk
killswitch11 said:
OK, got mine back up and running! I'll just leave what I did here in case anyone can benefit from it.
I first used Wug's Toolkit to download and install the RAW drivers. (Option #4, I believe) They were the only ones that worked for me. I followed the instructions to install them and then when it looped to the No Command screen, I held volume up and power. This got me to the menu, where I chose reboot. I then immediately held down the volume button and power to get into the bootloader screen, where it (thankfully) stopped looping. Then I unlocked the bootloader using the one-click option. Next step was to download and flash factory 4.4 image using the Soft Brick mode. Fastboot recognized my device and pushed the image. Now all is well. Close call... I've already enabled USB Debugging for my wife on this tablet so that crap doesn't happen again. She did lose all her data but she is happy to have a working tablet again instead of a $200 beer coaster.
Click to expand...
Click to collapse
I'll give that a go tomorrow. Missed my tablet! Hope it works!
So my nephew brings me his galaxy s6 t-mobile phone... He forgot his lock pin so he factory reset it. Now he can no longer get into the phone because he doesnt know the correct email or password. I did some digging through the net watched a few videos... and found none of the methods they used to bypass the lock would work on his phone. Then I read about the Combination Rom (Factory Binary)... At this time I do not have any windows pc's and my VM will not read the usbs of the phone... (im not that experienced with vm to set this up) So i grabbed JOdin for linux and proceeded to try to flash the binary. However, JOdin did not work for me. So i found Heimdall and installed to learn that i had to find some weird way to run it as SU for it to work... Tho Heimdall worked like a charm.... With Heimdall I had to take the rom and completely extract it to a folder and find all the img files in it to install on heimdal like sboot, boot, cm, system, and quite a few others as well.I used the "PIT" file from the combination rom (which came in the download). When done installing the phone boots into Factory Binary... Interesting little rom... From here you can access settings, tho the instructions tell you to enable developer options and turn on usb debugging... in this rom they are set on by default i believe, so that was kind of a waste of time... then from the main menu you click the icon that looks like a calculator and type in "*#0808# where you are then presented with usb options. Select the last one on the list with adb at the end of it, click save and reboot. At this point I thought i was supposed to install the stock rom back (that was where i was lost) however all you have to do is let it boot back to binary. After it has reloaded... plug it into the pc and send it the proper adb instructions to disable frp lock. Techeligible has a batch file for use in windows, however if you dont have windows like me that does no good... So I went into the batch file with a text reader and extracted the information i needed ( 3 adb commands).In terminal i made sure my adb and fastboot were updated and working. I learned that when you type "adb devices" it will show the phone and if it says nothing else you are good to go. However it may give you a problem with permissions. If this is the case then unplug and make sure usb debuggin is on, you can also check that the adb is enabled again by doing the *#0808# command again and make sure the last selection is checked. When all is in order... At first I thought all commands must work for it to succeed... However this is not true at all. Only one of the adb commands will not give an error and at that time you can reboot into download mode and install the stock rom back on. After installation the phone will reboot and FRP Lock is no longer on... Now you can go into settings open up developer settings (tap build number till it unlocks) and select "OEM Unlock" and turn it on. Make sure usb debugging is on and you can boot back into download mode and install TWRP without a hitch.
I tried installing a couple of custom roms, however I have had no success with getting one to boot. (always stuck in boot loop even with wipe or factory reset) so I gave up and left him with the stock rom. If anyone has any idea of how i could get passed the bootloop maybe i can try again for him sometime and see how he likes various custom roms, but now he is happy he has his phone back working and it only took me a week of off and on frustration to figure it out... Hope this helps someone... (please dont ask for links) but if you do need help or have questions feel free to ask.