Well I flashed by the firmware 2.22.1540.3 through hboot and now my phone is stuck on on the bootsplash screen I can boot into bootloader mode. My computer doesn't recognize that a device is connected so I can't use adb and I tried flashing twrp by using a custom ruu in hboot but it didn't work. Anyone know how to get a custom recovery and flash a custom ROM? Thanks in advance. I'm s-off and I have an unlocked bootloader and the zip was modified for my CID (CWS__001)
Does fastboot mode work? That's the best way to flash a recovery.
As far as the rom goes, you'd need to adb sideload or from twrp adb mode. Or I recently did it using a micro SD. I put the rom on the microSD with my tablet, poured out in the phone and flashed with twrp.
View my profile, I dare you. ?
KJ said:
Does fastboot mode work? That's the best way to flash a recovery.
As far as the rom goes, you'd need to adb sideload or from twrp adb mode. Or I recently did it using a micro SD. I put the rom on the microSD with my tablet, poured out in the phone and flashed with twrp.
View my profile, I dare you. ?
Click to expand...
Click to collapse
I can boot into fastboot but the computer doesn't recognize the device it beeps to show a device is connected but nothing else happens and on fastboot it changes from fastboot to fastboot USB
Rafa2745 said:
I can boot into fastboot but the computer doesn't recognize the device it beeps to show a device is connected but nothing else happens and on fastboot it changes from fastboot to fastboot USB
Click to expand...
Click to collapse
That's what it's supposed to do.
In a command prompt... Navigate to the folder fastboot is in and type "fastboot devices". If it returns a number, you're good to go! Flash recovery.
View my profile, I dare you. ?
KJ said:
That's what it's supposed to do.
In a command prompt... Navigate to the folder fastboot is in and type "fastboot devices". If it returns a number, you're good to go! Flash recovery.
View my profile, I dare you. ?
Click to expand...
Click to collapse
It says 'fastboot' is not recognized as an internal ir external command operable program or batch file. My computer is windows 8
Rafa2745 said:
It says 'fastboot' is not recognized as an internal ir external command operable program or batch file. My computer is windows 8
Click to expand...
Click to collapse
Are you in the fastboot folder? Doesn't sound like it. If you type "dir" you should see fastboot. Exe .
If you're having trouble, and don't know fastboot... You might need to read up first.
View my profile, I dare you. ?
---------- Post added at 08:18 PM ---------- Previous post was at 08:17 PM ----------
Your recovery zip should be in that folder as well.
View my profile, I dare you. ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
Until you get numbers returned from the fastboot devices command.... You can't do anything.
View my profile, I dare you. ?
KJ said:
Are you in the fastboot folder? Doesn't sound like it. If you type "dir" you should see fastboot. Exe .
If you're having trouble, and don't know fastboot... You might need to read up first.
View my profile, I dare you. ?
---------- Post added at 08:18 PM ---------- Previous post was at 08:17 PM ----------
Your recovery zip should be in that folder as well.
View my profile, I dare you. ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
Until you get numbers returned from the fastboot devices command.... You can't do anything.
View my profile, I dare you. ?
Click to expand...
Click to collapse
thank you very much I fixed it.
Awesome!
View my profile, I dare you. ?
Related
I got a relocked HoX and now it says: [Preload] Failed to open usb master mode.
Problem is, it doesn't boot, I can't run RUU and I can't unlock it because adb does not find the device.
So it this state it is unusable.
Can anyone please help me?
Thanks in advance
Edit: ADB can't find the phone, so I can't flash files or unlock the phone. However it does react on getvar and reboot commands...
Amicushia said:
I got a relocked HoX and now it says: [Preload] Failed to open usb master mode.
Problem is, it doesn't boot, I can't run RUU and I can't unlock it because adb does not find the device.
So it this state it is unusable.
Can anyone please help me?
Thanks in advance
Edit: ADB can't find the phone, so I can't flash files or unlock the phone. However it does react on getvar and reboot commands...
Click to expand...
Click to collapse
hold power+volume down until you get in white bootloader screen
then use fastboot oem unlock command
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
You don't need adb at all to do flash anything
You can use: fastboot oem rebootRUU
Also to reboot: fastboot reboot
Flashing is done in recovery btw.
Vcek said:
hold power+volume down until you get in white bootloader screen
then use fastboot oem unlock command
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
You don't need adb at all to do flash anything
Click to expand...
Click to collapse
tomascus said:
You can use: fastboot oem rebootRUU
Also to reboot: fastboot reboot
Flashing is done in recovery btw.
Click to expand...
Click to collapse
Thanks for the replies guys, fixed it thanks ! Awesome!
hello
i have Assu Nexus7 (K008)
when i power on just hang on google logo , i try to hard reset no succed ,so i need to flash the tablet
the problem there is no micro-sd card slot so any way to flash it ,there is any program i can use ?
Try this...
http://forum.xda-developers.com/showthread.php?p=44202509
Sent from the "DOG" pound
i will try and post result
thx bro
i try don't work , he can detect the tablet but unable to flash it !!
hitibiti said:
i try don't work , he can detect the tablet but unable to flash it !!
Click to expand...
Click to collapse
I would ask for help in that thread there's way smarter people than me going to that thread..
Sent from the "DOG" pound
ok , thx for your help i will continue searching
Try not to post in Development sections again.
As for the problem, does your N7 have a custom recovery installed?
If yes, just boot into recovery, plug it into your PC and ADB sideload a ROM from your PC onto your N7. How you can do an ADB sideload depends on what custom recovery you have, and can be found on the web if you search.
If no, just install one ASAP and do the rest
Sent from Google Nexus 4 @ CM11
i don't know tablet came hang on star-up logo
i can enter to recovery, but how can i drug the file to tghe tablet if i can't chose install form ...
i try i alot of time not succeed
waiting for help
Try flashing a custom recovery and manually flashing a new image
sent from my nex7
mugzylol said:
Try flashing a custom recovery and manually flashing a new image
sent from my nex7
Click to expand...
Click to collapse
that's i would like to do but the problem how can i do that my tablet don't have micro-sd card so there is software can link tablet to pc for Flashing ?
You can open a command window on the platform tools folder inside the android SDK (here) http://developer.android.com/sdk/index.html by holding shift on it and right clicking. Click open new command window here. Go into fastboot mode on your tablet. There is a command to flash a .img which is fastboot flash (or fastboot boot if you do not want to flash) then after fastboot flash or boot you put the name of your recovery followed by .IMG (it has to be a .IMG file) the recovery needs to be in the platform tools folder for this to work. From your recovery you can flash an image but it needs to be on the internal SD(so this probably won't work)
sent from my nex7
mugzylol said:
You can open a command window on the platform tools folder inside the android SDK (here) http://developer.android.com/sdk/index.html by holding shift on it and right clicking. Click open new command window here. Go into fastboot mode on your tablet. There is a command to flash a .img which is fastboot flash (or fastboot boot if you do not want to flash) then after fastboot flash or boot you put the name of your recovery followed by .IMG (it has to be a .IMG file) the recovery needs to be in the platform tools folder for this to work. From your recovery you can flash an image but it needs to be on the internal SD(so this probably won't work)
sent from my nex7
Click to expand...
Click to collapse
but to do that i need have unlocked boot loader ? or i can repair it with lock boot loader too ?
I heard that you could flash a recovery without an unlocked bootloader but if you want to unlock your bootloader type fastboot oem unlock in the the command(while in fastboot) window and you will be asked if you want to unlock Select yes with the volume keys and the on button
sent from my nex7
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
I'm pretty sure this requires the devices USB drivers which can be downloaded here http://developer.android.com/tools/extras/oem-usb.html right click your tablet in device manager program, press update drivers and browse for the USB drivers (need to be extracted).
sent from my nex7
---------- Post added at 05:58 PM ---------- Previous post was at 05:11 PM ----------
PS: windows come with device manager, just search for it
sent from my nex7
mugzylol said:
I heard that you could flash a recovery without an unlocked bootloader but if you want to unlock your bootloader type fastboot oem unlock in the the command(while in fastboot) window and you will be asked if you want to unlock Select yes with the volume keys and the on button
sent from my nex7
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
I'm pretty sure this requires the devices USB drivers which can be downloaded here http://developer.android.com/tools/extras/oem-usb.html right click your tablet in device manager program, press update drivers and browse for the USB drivers (need to be extracted).
sent from my nex7
---------- Post added at 05:58 PM ---------- Previous post was at 05:11 PM ----------
PS: windows come with device manager, just search for it
sent from my nex7
Click to expand...
Click to collapse
i try to do that when i type YES tablet hang and waiting nothing happen !!!!
Did you install device drivers?
sent from my nex7
This saved my Nexus 7 2013. It would not boot, I could not flash, format, copy anything, etc. The dreaded spinning Google symbol. It would give me errors when trying to flash. I tried TWRP and CWM, nothing would flash. I ran the Dead_Nexus7.bat file from the link below and my Nexus worked. It was like magic bringing it back from the dead. I am assuming the problem occurred when unlocking the device. It froze for a minute or two, until I started tapping on it.
http://forum.xda-developers.com/showthread.php?t=2381582
yes all driver installed properly , after type fastboot oem unlock i press yes on tablet and after seem like tablet hang !!
Hmmm. You actually don't need an unlocked bootloader to flash a recovery so just run the fastboot boot or fastboot flash
sent from my nex7
---------- Post added at 07:43 PM ---------- Previous post was at 07:38 PM ----------
If you were to flash a new ROM you would need to flash it through the recovery as a .zip. Does the computer find the internal SD?
sent from my nex7
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
I also think I know why it gets stuck. I think it is because it cannot mount the sdcard partition to earase the userdata contained on it (there is none but the computer doesn't know that)
sent from my nex7
---------- Post added at 07:45 PM ---------- Previous post was at 07:45 PM ----------
Flashing a new ROM will remount the sdcard partition
sent from my nex7
no, computer can't find internal SD ram , and as you say you boot loarder must be unlocked and i didn't find any way
so i am still wait for help thx
Read this tread for a 2012 model. It shows that a new os recovery bootloader and kernel can all be flashed at once through fastboot commands to restore a tablet http://forum.xda-developers.com/showthread.php?t=2546558
sent from my nex7
Hi,
as i wanted to run the latest cm11 nightlies i updated my recovery system from ext4 to twrp and can not boot into the recovery mode now to flash anything. unfortunatly the volume down key is broken since years too, so if i do a normal boot the phone gets stuck with a black screen. its rooted, s-off and everything, i have been running almost every cm10 and cm11 nightly this and the past year just fine, just with android 4.4.4. i had problems now, thats why the new recovery was needed. now usb drivers are still working and i can see the phone with adb via adb devices. but as soon as i type adb reboot recovery or adb reboot bootloader the phone just does not respond anymore. i have basic knowledge of flashing roms, but i just cant figure out how to fix this problem. any expert here with a useful idea? would appreciate it very much, if i should add any additional information about the problem just reply what could help to fix this. thanks a lot in advance!
tldr: android 4.4.2 worked fine, updated recovery and wiped everything to flash 4.4.4, cant reboot into recovery now anymore
Fix it?
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
Sounds to me like you need to reinstall the drivers. You have to go into platform tools in SDK and open a cmd prompt there. In there you will be able to access bootloader
marknoll said:
Fix it?
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
Sounds to me like you need to reinstall the drivers. You have to go into platform tools in SDK and open a cmd prompt there. In there you will be able to access bootloader
Click to expand...
Click to collapse
thanks for the idea, you get my hopes up. could you explain please how to open a cmd prompt in the sdk and access the bootloader from there?
OK. Find your SDK folder. Right click it,open file location. Find platform tools,right click it, open file location. Inside tools, hold shift right click and chose open cmd prompt here
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
When done, type fastboot devices see if PC sees the phone. There u will be able to flash the new recovery.
---------- Post added at 06:21 PM ---------- Previous post was at 05:29 PM ----------
Did you figure it out?
marknoll said:
OK. Find your SDK folder. Right click it,open file location. Find platform tools,right click it, open file location. Inside tools, hold shift right click and chose open cmd prompt here
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
When done, type fastboot devices see if PC sees the phone. There u will be able to flash the new recovery.
Click to expand...
Click to collapse
allright i`m in the fastboot commandline and i see the devicename when i enter "adb devices". how can i flash and boot into the recovery now? sorry for the n00bquestions and thanks again :\
i got the file on the sd card already, twrp worked fine. just after the fullwipe nothing worked anymore
You have to be in fastboot mode
---------- Post added at 06:25 PM ---------- Previous post was at 06:24 PM ----------
OK adb reboot boot loader..copy and paste the recovery in that platform tools folder(after loading boot loader) type fast boot devices.
---------- Post added at 06:32 PM ---------- Previous post was at 06:25 PM ----------
If PC sees the device after entering fastboot devices. Then u may be able to flash the recovery.
Fastboot flash recovery "image file name."
marknoll said:
You have to be in fastboot mode
---------- Post added at 06:25 PM ---------- Previous post was at 06:24 PM ----------
OK adb reboot boot loader..copy and paste the recovery in that platform tools folder(after loading boot loader) type fast boot devices.
Click to expand...
Click to collapse
the phone doesnt go into the boot loader. if i enter adb reboot boot loader it just does nothing
I suggest u run the ruu then. Start over. Are unolcked boot loader? If so, relock boot loader and run ruu.. U will have to unlock boot loader after the ruu though
---------- Post added at 06:40 PM ---------- Previous post was at 06:35 PM ----------
You have to type adb reboot bootloader. Like that exactly
marknoll said:
I suggest u run the ruu then. Start over. Are unolcked boot loader? If so, relock boot loader and run ruu.. U will have to unlock boot loader after the ruu though
---------- Post added at 06:40 PM ---------- Previous post was at 06:35 PM ----------
You have to type adb reboot bootloader. Like that exactly
Click to expand...
Click to collapse
yeah i typed it like that, the phone just doesnt react. i will read what you mean with ruu and try all that. thank you for your help, maybe the phone isnt bricked
If you can't access bootloader ,more than likely its bricked
You can't ruu if you can't access bootloader.
Ok first i have no clue as to what some of this means but here goes ........my little brother assured me he could make my kindle better so he in his words........ he use an app call flashify and flash twrp as the rom on my fire then wiped all data there is no back up can this be fixed remember im no tech person.
dumbdumb12 said:
Ok first i have no clue as to what some of this means but here goes ........my little brother assured me he could make my kindle better so he in his words........ he use an app call flashify and flash twrp as the rom on my fire then wiped all data there is no back up can this be fixed remember im no tech person.
Click to expand...
Click to collapse
What does it do from power off (hold power button 15-20 secs)
Do you know which kindle fire it is, does it have HD on it?
Sent from my XT894 using Tapatalk
if you hold power button it turns off ......when you power on it powers straight to twrp screen.......it is first Gen no HD 6.3.3
If you have twrp you can fix
Sent from my XT907 using Tapatalk
---------- Post added at 05:37 PM ---------- Previous post was at 05:05 PM ----------
You should download adb/fastboot files from my Flashing Twrp in FFF bootloader with fastboot.exe
Step 1:
download adb-fastboot.zip
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, and fastboot.exe to adb folder.
Step 2
install Kindle Fire drivers
check drivers, open device manager, kindle should be listed
android phone>android adb interface
if not see my Driver links / Errors /verify drivers are installed correctly
if drivers are correct
Step 3
Open a Command Prompt (start>all programs>accessories>Command prompt)
change directory to adb folder with
Code:
cd\adb
adb devices
should get a return code back something like
Code:
123456789abcde recovery
if so enter
Code:
adb shell "cat /proc/cmdline"
post code returned in this thread
mem=512M console=null androidboot.selinux=permissive
dumbdumb12 said:
mem=512M console=null androidboot.selinux=permissive
Click to expand...
Click to collapse
should be
Code:
console=ttyO2,115200n8 [email protected] init=/init vram=5M omapfb.vram=0:5M
what twrp version?
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
could just be the twrp version, only the kindle fire 1 has 512mb of memory
twrp 2.8.1.1.o .......he flashed this as the rom not recovery lol
dumbdumb12 said:
twrp 2.8.1.1.o .......he flashed this as the rom not recovery lol
Click to expand...
Click to collapse
shouldn't matter, but 2.8.x.x twrps are not complete, adb is flaky at best.
try to mount sd card
select Mount> check sd card> mount usb
do you get a removable disk pop up?
sd_shadow said:
shouldn't matter, but 2.8.x.x twrps are not complete, adb is flaky at best.
try to mount sd card
select Mount> check sd card> mount usb
do you get a removable disk pop up?
Click to expand...
Click to collapse
no nothing pops up
dumbdumb12 said:
no nothing pops up
Click to expand...
Click to collapse
try to push file
download zip-otter-twrp-2.2.2.1-blaze.zip
and push with
Code:
adb push zip-otter-twrp-2.2.2.1-blaze.zip /sd card
command pompt did all kinds of stuff but kindle did nothing
does zip-otter-twrp-2.2.2.1-blaze.zip show up in sd card?
advanced>file manager> /sdcard
---------- Post added at 06:40 PM ---------- Previous post was at 06:38 PM ----------
dumbdumb12 said:
command pompt did all kinds of stuff but kindle did nothing
Click to expand...
Click to collapse
yah, adb is not working correctly, probably next step is getting a fastboot cable Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
No
could try
in the reboot options choose fastboot or bootloader
and flash the bootloader and twrp like in the Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
---------- Post added at 07:40 PM ---------- Previous post was at 06:47 PM ----------
stock bootloader is just the kindle fire boot logo, I have no idea if selecting reboot>bootloader will cause it to stay in bootloader or it will continue to TWRP
to test use
Code:
fastboot devices
I would send command just before selecting reboot>bootloader
I was using ressurction remix and had a latest dirty update via twrp and my phone was encrypted automatically. After that when I wish to use the fastboot mode and flash miui 10 beta version through miflash tool whenever i press on refresh of miflash tool the phone automatically disconnect and on the phone top left screen a message is shown "press any key to power off/shutdown".
I am not able to flash miui 10 through miflash and not able use any fastboot commands.
The only command i can use "fastboot devices"
Other than that phone automatically get disconnected.
I am using minimal adb and fastboot 1.4.3
harrry7492 said:
I was using ressurction remix and had a latest dirty update via twrp and my phone was encrypted automatically. After that when I wish to use the fastboot mode and flash miui 10 beta version through miflash tool whenever i press on refresh of miflash tool the phone automatically disconnect and on the phone top left screen a message is shown "press any key to power off/shutdown".
I am not able to flash miui 10 through miflash and not able use any fastboot commands.
The only command i can use "fastboot devices"
Other than that phone automatically get disconnected.
I am using minimal adb and fastboot 1.4.3
Click to expand...
Click to collapse
Boot to twrp format data and wipe cache. Boot to fastboot and try other usb 2.0 port.
My problem was solved by reinstalling the adb and fastboot in win 10 .
But thanks a lot for your suggestion.
bro is your problem get solved
---------- Post added at 10:16 PM ---------- Previous post was at 10:11 PM ----------
harrry7492 said:
My problem was solved by reinstalling the adb and fastboot in win 10 .
But thanks a lot for your suggestion.
Click to expand...
Click to collapse
bro how did you just do that reinstallation of adb and fastboot
Hello help me
aycs said:
bro is your problem get solved
---------- post added at 10:16 pm ---------- previous post was at 10:11 pm ----------
bro how did you just do that reinstallation of adb and fastboot
Click to expand...
Click to collapse
hola lograste resolverlo??