Hi Everybody,
I would root my phone but now I'm lock on the bootloader and when I want execute the command "fastboot flash boot boot.img" or system, etc, I've for answer "failed(remote: partition table doesn't exist)", but if I do it with the suffix _a, that's working (only on the pc; on the phone nothing happend).
Help me please; I can't flash nothing and I can't going on the recovery mod; I don't know what i need to do....
Related
hi , first of all , sorry for my bad english
im have bought htc one v last week
so last night i tried to root and install custom rom
after i unlock the bootloader and rooting the device from this thread http://forum.xda-developers.com/showthread.php?t=1598964
then im choosing the custom room made by shubhamchamaria (thanks ) at http://forum.xda-developers.com/showthread.php?t=1640995
before i flash the room , my device still can access the boot loader
after flash the boot.img
then im entering the cwm recovery . then im installing the custom rom ,
so i did the reboot process
after the reboot process , it stuck at htc one logo (bricked?)
so i turn off the phone , turn off while pressing the volume down , it didnt enter the bootloader , but directly enter the cwm v5 recovery
so it bricked ? or another issue?
im downloading the stock rom right now
fyi ,
in the cwm recovery , ive format the data , cache partition and dalvik cache
thanks for the help
After you flashed the boot.img, did you do the "fastboot erase cache" ?
Not sure whether the boot.img that you have is secured or insecured, you can try this:
in CWM recovery, connect the usb cable to PC.
then go to your adb folder, in command prompt:
adb devices
if your device is listed, then the adb works
adb reboot bootloader
if it works
go to fastboot folder, in command prompt
fastboot erase cache
fastboot reboot-bootloader
So i tried to get stock rom back on my htc one m8 which is locked to ee and is a uk phone. I cant seem to get past the bootloader page the white fastboot screen.
Please help me.
You'll need to give a little more information rather than "tried to get stock ROM".
What did you do, what did you flash, are you S-On or S-Off? Have you somehow wiped the /system partition? Do you have a custom recovery installed currently?
Have you even unlocked the bootloader?
EDIT: I have to go now. I'm not sure what situation you're in. I don't normally suggest people use Toolkits and the like, but if you are in difficulties, in the first instance do a search (I doubt if you are the first person to have been in whatever position you are in). If you can't sort yourself out from the results, then have a look at this thread.
nobnut said:
You'll need to give a little more information rather than "tried to get stock ROM".
What did you do, what did you flash, are you S-On or S-Off? Have you somehow wiped the /system partition? Do you have a custom recovery installed currently?
Have you even unlocked the bootloader?
Click to expand...
Click to collapse
S-ON i think the system partion is whiped because i cant do anything other than fastboot the bootloader is locked so i cant get into a custom recovery. I was following a youtube video on how to get back to stock after rooting the the guy had me do a oem command in fastboot.
OK. But I'm not sure that you have actually wiped your /system partition.
Before you do anything, in fastboot mode (the white screen with the mutli coloured writing on it), type the following in a command prompt from the fastboot folder/directory on your PC, then press enter:
Code:
fastboot erase cache
and if that does nothing
Code:
fastboot wipe cache
Then try to reboot by typing
Code:
fastboot reboot
and hit enter.
If that doesn't work, grab the toolkit I linked to and you'll want to
1. Unlock bootloader
2. Flash custom recovery (choose TWRP)
3. Sideload ROM from recovery and follow the relevant instructions in recovery (You'll need to download a ROM to your PC and place it in the relevant directory)
Hello guys, a friend of mine has a galaxy nexus with some problems.
When I turn on the phone, it starts booting normally, but a few seconds after getting into "desktop" it starts popping up errors saying that the process as stopped.
I've already tried a few things, but without success. I'm running out of ideas and here I'm asking for your help.
Things I've tried:
-Boot into recovery mode and wipe all data.
The phone says that the operation completed successfully, but after rebooting the phone remains the same. All apps, wallpaper, lock screen, etc. It seems that nothing was changed by this process.
-Flash a original google ROM
Following the tutorials, the first step is to unlock the bootloader with fastboot oem unlock. The phone shows a confirmation asking if I want to unlock it, I say yes, and it shows "status: unlocked". But after rebooting the phone it is locked again!!!
I tried to flash the room without rebooting the phone after unlocking it,
Code:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxla02.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-takju-imm76i.zip
The first command to flash the bootloader also says that completes successfully, but when I'm flashing the radio it will complain saying that the phone has the wrong bootloader version installed.
-Flashing via Odin
It fails when is flashing system.img to the phone
-Flash custom recovery - fastboot flash recovery recovery.img
The process completes "successfully" but when I boot into recovery mode, there is the original one and not the one I just flashed.
-emmc brickbug - partition scanner
I found this thread http://forum.xda-developers.com/showthread.php?t=1823918 and tried to run the partition scanner. As I can't have the phone on enough time to use adb shell, I tried to use this scanner via adb sideload but the phones returns an error when running it. (probably because it doesn't have busybox installed, not sure)
After trying all of steps above, the phone is still the same... nothing changed. Once, I managed to connect it to the pc as an usb storage device, and was able to copy some photos from the phone and deleted them. But after rebooting they were all there again. It seems that all write changes are not persistent.
I'm out of ideas now... Do you have any idea of what is the problem? Or any suggestion for me to try?
Thanks in advance
I believe that there is a script in the android SDK tools called flashall.bat which will reflash the kernel, bootloader, recovery, ROM ect. I'm not sure how to use it, but you could potentially try that
Hi, thanks for you suggestion, but unfortunately it didn't work.
I had a look at the flashall.bat script and it runs the same commands I run manually.
I think that the phone might have some hardware problem... Normally I would buy a new phone, but I'm trying to fix it because it is important for my friend and for me because it is challenging.
I guess that the next thing I will try, will be trying to run emmc_find_brick script by @hg42 via sideload
Try formatting /system and reinstall android. Power your device into bootloader mode. Make sure your device is unlocked. Also, make sure you have the factory image downloaded. After your device is plugged in into your computer, use this fastboot command: fastboot erase system. This will delete everything from /system. Also format /data and /cache: fastboot erase data and fastboot erase cache. After that, try installing the factory image again.
I can boot on to the phone and use it fine but when I try to access TWRP so I can actually root the phone it flashes the entering recovery pink text for a split second then goes to fastboot. I have an unlocked bootloader and the last commands i put into the console were, fastboot flash recovery twrp-3.0.2-0-m8.img and fastboot erase cache. If you need any other info let me know, I need any help I can get!
Hi everyone,
I´ve been trying to install twrp recovery in my Huawei Ascend P6 via fastboot. I followed this "techglen adb and fastboot guide"
I already installed everything needed for adb conection.
So I connect my phone in MTP mode and use "adb devices" and my device appears normally, but the problem happens when I reboot into Bootloader/Fastboot mode and use "Fastboot devices" it appears a device conected but with a bunch of "?????" and a smiley face at the end like this:
C:\Fastboot>adb devices
List of devices attached
123456789 device --------> bunch of numbers appear normally
C:\Fastboot>adb reboot bootloader --------> Phone restarts into bootloader mode (shows huawei ascend logo)
C:\Fastboot>fastboot devices
????????_?_???_?<??????? fastboot ----------> WTF (this is exactly what appears)
I would like to know if there's something wrong with my phone
Should I proceed and flash the custom recovery?
I have stock android 4.4.2 (rooted with kingroot) and stock recovery.
I am a total noob at this so I need your help :crying: I dont want to do anything stupid. (If already did let me know lol)
I have the same issue. Problem is that phone is bricked, so I can only enter in recovery (official, unrooted, unlocked) and fastboot mode.
Have you managed to solve or have some hint?
I have experienced a inconsistency while using minimal adb and fastboot. While device not showing i could send command and the phone would respond. After going into bootloader and while my device wasn't shown in the list i could flash twrp without much trouble, helped me go back from being stuck on bootanimation. used the command fastboot flash recovery xxxx.img (where xxx is the name recovery name). If you can get into boot loader try fastboot reboot bootloader and if the phone responds you might be in the same situation i was.
Always remember: Messing with recoveries bootloaders and boot images might make your phone unusable so do it at your own risk
Have you actually tried to flash twrp? Did you put the img file of twrp to the minimal adb and fastboot folder? If so, try the commands 'fastboot flash recovery recovery_twrp.img(<-- use the name of twrp file here, so not the exact name wrote here) and reboot. My phone is a bunch of question marks as well and it flashed twrp just perfectly (I got it frome here: http://forum.xda-developers.com/showthread.php?t=2632542)