I was trying to build a CWM recovery for Celkon Q 500, which is a Broadcom chip based mobile(BCM 23550) by following some guides from internet. After finishing it, I tried to test it without flashing it to recovery(because of fear). I used the command " fastboot boot recovery_cwm6032.img ". It produces a result like this ;;--"downloading 'boot.img'...
Okay [0.312s]
booting...
FAILED<remote : boot command not supported>
finished. total time : 0.328s
What does this mean? Does it mean that my mobile or the OS of my mobile(android 4.4.2) does not support the fastboot command 'fastboot boot xxx.img' or the is something wrong inside the recovery_cwm6032.img?
I had tried to get a CWM recovery at 'builder.clockworkmod.com', but as reported by many I also did not get any result.(a new web page opens after clicking 'continue to build server' that shows "HTTP ERROR 404
Problem accessing /job/recovery/. Reason:
Not Found ".
Please help.
Related
I've usually managed to solve all my problems with searching around, but I seem to have hit a roadblock this time. I'll try to describe the problem as crisp as i can.
What is the state:
On turning on the phone, the phone gets stuck with this error message:
Failed to boot 1
PwrReason: PWR_KEY_PRESS
Starting Fastboot Protocol Support
If I push the volume down and try to start, it's stuck with this message:
Failed to boot 1
Entering NvFlash Recovery Mode
How I reached this state:
It happened immediately after I installed this app from the play store:
NavFree (World)
On starting the map, it asked my for the country to download, followng the selection of which it downloaded a ~128MB download. At the end of the download, the phone went blank. Nothing worked, so I had to do a hard reboot. After the reboot, I am in said state.
What I have tried:
I have the following sbfs:
1ff-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-att-us-gas_na_olpsgbattspe_p011.sbf
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012.sbf
att-2.3.4_pudding_preroot
I first tried flashing with the 2.3.4 stock, and later with others. RSD finishes btu says fail.
No sd card, no sim card. I am not a noob, but not very much better either.
Versions:
Driver: 5.4.0
RSDLite: 5.6
Any help is appreciated.
Edit:
I realize that I am able to put the phone into fastboot mode by holding the vol + key when powering on. So i download and tried some commands.
The devices command comes back with a serial number result.
But the following commands:
moto-fastboot erase boot
moto-fastboot erase system
error out, both on the phone and in the pc as follows:
PC: erasing 'boot'... FAILED (remote: (00180001))
PH: Failed to process command erase:boot error (0x180001)
Wow.. No replies in 24 hours?
Is my post even in the correct section - mods, please help move to right place.
hello,
part 1
I will start by that the LG G3 I got from a neighbor and she did not exactly know what her boys do to the device :angel:
I do not know if the device was in debugging mode and ROOT so I will describe the current situation:
1 If you turn on the device is stuck the logo of LG
2 he can get into a normal recovery, but after I perform Clear / Reset is back to being stuck in the logo.
3- When I try to enter download mode he entered to fastboot mode Started and wait for fastboot Processsing command.
4- My computer installed SRKtool_2.1 droidth and SRKtool_1.0.5_droidth, as well as SDK is updated.
5- I tried to make various adjustments through SRKtool and via fastboot command, the file (*.bin\*.img) send to the device from the PC but faild to write them, and I get messages:
sending laf "okay"
writing laf "failed (remote: flash write failure)
all file have the same masssage.
I try to perform repair to:
A- fastboot mode Started
B- recovery mode
from srktools and I got the same write fail massage !
He's trying to re-write the BIN files taking off from the original rom,
again he can transfer files but does not actually write the on the device,
then the device restarts and then he stuck the logo of TWRP, the expense of battery re-enters the regular recovery mode.
part 2 Updated!
From time to time the device did not enter the FASTBOOT MODE and gets to the firmware update, I install a new ROM, but !!!
the operating system install LGE Android MTP Device driver,
when I flash the rom he stack on 3% and the hardware driver turn to yellow with code 10 (device not work properly).
does LGE Android MTP Device have to be install to do the FLASH ???
the MPT can be damage and that cause the problem ?
the same problem on 2 different PC & OS (xp/7/10) with different drivers for MPT,
after you restart the mobile it returns to FASTBOOT MODE
guys, i have huge problem… somone tried to install TWRP recovery on my G8800 & now i cant do anything with him…. when i tried to install another recovery [via fastboot mode] i get the following error: FAILED (remote: partition 'recovery' not support flash)… what could i do? [i dont have any rom on the phone either...]
folks im at my nerves end... (hello btw)
firstly a thousand apologies to the mods if im posting this in the wrong place and a thousand apologies more to the rest of you for asking a question that has probably been answered time and time again.....
I can't get round it, iv been able to unlock bootloader and I thought that would have been the hardest part.... but I think I cant get my hands on the right, up to date files, in order to root my current system... iv been doing a ton of reading and just as many rooting attempts on my phone but to no avail......
the closest iv got in the command window was "error: device 'null' not found", to my understanding this is a driver related issue?...I dont know... if someone could hold my hand (im scared) and walk me through the process step by step I would be very, VERY grateful....
P.s; in exchange I can help you install CFW on a PSP.....lol right? (I actually made a pandora battery back in the day and im still rather proud of that)
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?
rootcheck says "root access is not properly installed on this device" still.....
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (14956 KB)...
OKAY [ 0.479s]
writing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.624s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8
.7.0-E6653-20151114_material.img
error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'
UPDATE:
So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....
after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....
I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!
FINAL UPDATE:
BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
Thanks for the updates, i will try to follow your guide. how did you finally achieve success ?
Hey Rath,
First off im not responsibly for any damage caused to your device by the following guide....
....on to business...
Assuming your phones bootloader is unlocked, you have correctly installed ADB tools and the drivers required, allowed USB debugging and you know your build number you'll need to head over to this site...
https://kernel.andro.plus/kitakami_r2.html
scroll down....there you will see two sets of requirements one for the Xperia Z5 [E6653 / E6603] and one for the Xperia Z5 Compact [E5823 / E5803]
we are interested in the compact requirements.... you'll see that it says "32.2.A.5.11 -> v42 -" this means that for build number 32.2.A.5.11 you will need kernel version 42....
so keep scrolling down once you've figured out what version you need and click on "google drive V32 and later" for the Xperia Z5 Compact this will open a page with all the files inside (google drive)...either hover over with your mouse each file until you find "Z5C_AndroPlusKernel_v42.zip" or organize the files by clicking "last modified" in list view, this should show you the most recent file (v42) at the top of the list....
once you have found this file DL it and extract it to your desktop...copy ONLY the "boot.img" file into your platform-tools folder (android->sdk->platform-tools)....
next you'll need a recovery file or "twrp" to go with that, so head on over here...
https://www.androidfilehost.com/?fid=24459283995304864
and download that file, again copy it to your desktop (no need to extract) then copy this file as well to your platform-tools folder......copy the exact name of the file(TWRP-3.0.0.0-suzuran without the .img part...if youre on windows the .img will not show anyway..)...you'll need it later...
next open the command window by clicking on an empty space IN THE PLATFORM-TOOLS folder, then press shift+right click and select "open command window here" this will open adb tools...connect your phone via usb cable to your pc if it not already connected and type in the command window "adb devices" and hit enter....you should see your device listed...
if so type "adb reload bootloader" your phone should turn off and boot into bootloader (a blue led light should show in the top right corner of your phone)
if so type "fastboot devices" and hit enter...your device should show again on the list...
if so then type "fastboot flash boot boot.img" this will flash the kernel V.42 to your system....
you should see a couple of "OKAY"s and the time it took to flash the device....
next type "fastboot flash recovery *right click after the space and paste the exact name of the twrp file you copied earlier*.img
E.g: fastboot flash recovery TWRP-3.0.0.0-suzuran.img
and hit enter.... again you should see a couple of "OKAY"s and flashing times....
if all goes well you want to then type "fastboot reboot", your phone should then reboot...once you see a yellow light turn on on the top right corner press the down volume key several times until you enter the TWRP recovery menu.... if so, and the twrp is stable (ie it doesnt turn off on its own and reload) then the hardest part is done.....
click "reboot" on your phone and then click "system"...this will reboot your phone, this time let it run to see if it doenst get stuck in a bootloop....once your phone has loaded you'll want to install superSU....
go to the play store and DL rootchecker.... run the app and it will most likely tell you that your system isnt rooted yet (because we havent installed superSu) so head on over here...
http://www.supersu.com/download
scroll down and DL Recovery "Flashable.zip"...then take the file WITHOUT EXTRACTING IT and put it in the SD of your phone... reboot into recovery using the command window (adb reboot recovery) or turn off your phone, turn it back on and when you see the yellow light click volume down button repeatedly....
once in recovery select INSTALL click on the ZIP file you just added and the phone will install supersu, once done reboot your system and VOILA! check with the root checker app if your phone is root and have fun!....
I found this video to help me out a lot....he uses really old files and is rooting an xperia z5 but its essentially the same....
https://www.youtube.com/watch?v=dTlosea6SJE&t=709s
SwisSwiss said:
UPDATE:........ So i think I was able to flash the proper Kernel (adroid plus kernal V42) but was unable to do flash recovery?
rootcheck says "root access is not properly installed on this device" still.....
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (14956 KB)...
OKAY [ 0.479s]
writing 'boot'...
OKAY [ 0.143s]
finished. total time: 0.624s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8
.7.0-E6653-20151114_material.img
error: cannot load 'twrp-2.8.7.0-E6653-20151114_material.img'
UPDATE:
So i was able to do a flash recovery by renaiming the twrp file to simply twrp and adapting the code typed in the command window...... this caused my phone to soft brick or enter a bootloop....
after some swearing and more reading I was able to do a flash recovery with twrp-3.0.2-0-E5823.img (again by typing the exact name of the .img file in the command window....duuhhhh).... this allowed my phone to boot properly (thank God)... but root checker still says "root access is not properly installed on this device".....
I feel as if im close to my goal, what am I doing wrong!?......that soft brick served me as a cold shower and a lesson....this is kinda fun!
FINAL UPDATE:
BOOOM!!! success..... only took me all day...... still one thing though, i was unable to back my system due to lack of space on my SD card.... am I boned in this regard or can I create a back up later?
Click to expand...
Click to collapse
i wonder if you backup the DRM keys\TA partition
In regards to why i was unable to create a back up right away? Not sure, think it was simply a matter of volume...
Had a crappy 4gb micro sd In there....
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
BoFar said:
Hi,
I'm newb in this forum and i'm looking for your advice and help,
my situation is as titled in the thread...my phone stuck on huawei logo...the situation starts when i'd tried to flash TWRP recovery..but it seems that was a wrong one...after then i erased system (stupid i was :crying: ) trying a factory reset (i'd downloaded the original stock)....this is when things gets worst ...now i can't get into recovery mode and the phone stuck on the logo...one last detail when the phone is turned on and usb connected to the PC the Hisuite seems identifying the phone but couldn't connect...
any help would be very appreciated
thank you all for your time,
Click to expand...
Click to collapse
FYI,
now i can get into bootloader but without a recovery...
with the already downloaded stock rom i'd extracted all IMG files from the UPDATE.APP.
the step where i'm stucking is that flashing system with fastboot gives this :
target reported max download size of 266338304 bytes
erasing 'system'...
OKAY [ 1.094s]
sending sparse 'system' (259466 KB)...
OKAY [ 17.422s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 18.547s
the system.img is 2.39 Go.
same things and messages happens with recovery & boot files [ FAILED (remote: size too large) ]
I thank you advising how to resolve this
[SOLVED]
Here's steps that I made (after a long search with Dr. GOOGLE ):
1- Download & install the Android Studio and its SDK tools (that include fastboot and adb latest version). when having the famous message of FAILED (....TOO LARGE) use the -S switch and be patient with SYSTEM.IMG since file size is big (first tries gave me the error message but after many try it works),
2- Download the official stock ROM from Huawei webpage,
3- Download Huawei Update extractor,
4- Extract BOOT.IMG & RECOVERY.IMG & SYSTEM.IMG from the UPDATE.APP extracted file,
5- flash sequentially : RECOVERY then BOOT then SYSTEM (Remember the reboot after each flash),
That's all...Folks