XDA Friends,
WOULD YOU LIKE TO MAKE A LITTLE MONEY TODAY???
I am calling out to you in DIRE need. I have royally screwed up my brand new Razer phone (US) and as far as I can tell there is only one way back and that is to get one of you gracious souls to do me a very big favor. What I need is a SD Card that has been formatted to work on a Razor phone and that contains, an ENTIRE cheryl-global-3005.zip. One that has not only the boot.img but the system.img. The reason I need to get this from one of you is that while I was in TWRP I accidentally flashed boot.img in System instead of Boot. This overwrote System and so now I cannot boot into the main system, it essentially goes into a boot loop. So that means I cannot get adb to work which means I cannot move files onto the SD Card (that is specially formatted for that phone and cannot be used to move files physically). And I failed to get the entire image onto the sd card prior to this happening so I do not have a system.img file on the phone in any capacity with which to flash to at least get back to factory.
So I'm thinking that if I can get someone to send me a formatted sd card that contains the full cheryl zip then I can put that card in my phone flash the system.img file from it that should get me back.
If you are willing to help me out with this I WILL PAY YOU.
PLEASE send me a private message here so we can arrange this as soon as possible. I'm phoneless without this fix.
You forgot to mention where are you from, my friend.
My advice comes free of charge:
Hold the power key until the device shuts off. Then download the system images from https://developer.razerzone.com/razer-phone-dev-tools/factory-images/
Unzip this file and run the flash_all.bat file. (I assume you have fastboot set up already considering you've flashed TWRP). Once this completes you should see it booting up to a stock system.
You also have the option of manually flashing the system.img from this factory image using fastboot. No SD card required
Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.
Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.
OK scratch that I am able to get into download mode now. @Flippy125 thanks for the advice. I'll give that a try.
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
I think you meant "fastboot flash system_a system.img"
And you don't need to do "fastboot flash flash_all.bat", you just double click flash_all.bat that is inside the folder and it should work, as long as you have fastboot correctly installed
EDIT: I'm not sure, but I think "flash_all.bat" would erase all your files. Can anyone confirm this?
lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
fastboot flash system system.img
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
lostnsound said:
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
Click to expand...
Click to collapse
I'm not sure, but I think those are partitions like C:/ and D:/ on a PC.
"System_a" would flash system.img only on Slot A, "System_b" on Slot B, I don't know what "system" does....i think it flashes both
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
lostnsound said:
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
Click to expand...
Click to collapse
I'm glad that it worked. Just enjoy it!
Reading this brought a warm feeling to my heart. Have fun with the phone. It's great!
Glad this got sorted. I think I can speak for all of us tinkerers when I say we've all been in this situation before and called upon the forum for advice. Pay it forward ^_^
Related
Hey, and thank you all here on the forums for all the guides and helpful information.
I am completely new at android rooting, flashing and all that comes with this, though I've read up quite a bit.
Now, my tablet is running the 4.2.1 build "JOP40D.WW_epad-10.6.1.14.10-20130801" which i've found can not be rooted in certain ways, so I went for the fastboot.
I've made sure everything was as should be, far as I can tell from what I've read here:
Tablet prepared:unlocked, usb debugging checked
adb and fastboot ready
correct drivers
latest twrp blow(openrecovery-twrp-2.6.3.2-tf700t.blob)
Then, as I put in the final command "fastboot -i 0x0B05 flash recovery twrp.blob" I get the message "error: out of memory" and the fastboot.exe crashed.
What could be causing this? Don't really want to try over again since I have no idea what I might be doing wrong and I really don't want to end up with the hassle of a bricked tablet.
Could it be an issue with the twrp version, and its compatibility with the tablet?
There is no lack of available memory on my computer, and there shouldn't be problems with the tablet's ROM or RAM, as it runs fine except for the obvious problem this tablet has. Previous to unlocking it was wiped and reset to stock 4.2.1 Jelly Bean with the .10 build.
The CMD window looks like this:
"
C:\users\Hbryne.Hbryne-PC>fastboot devices
015d2d431f240415 fastboot
C:\users\Hbryne.Hbryne-PC>cd c:\android-adb
c:\android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
error: out of memory
"
Thanks in advance for any helpful reply!
HBMoe said:
Hey, and thank you all here on the forums for all the guides and helpful information.
I am completely new at android rooting, flashing and all that comes with this, though I've read up quite a bit.
Now, my tablet is running the 4.2.1 build "JOP40D.WW_epad-10.6.1.14.10-20130801" which i've found can not be rooted in certain ways, so I went for the fastboot.
I've made sure everything was as should be, far as I can tell from what I've read here:
Tablet prepared:unlocked, usb debugging checked
adb and fastboot ready
correct drivers
latest twrp blow(openrecovery-twrp-2.6.3.2-tf700t.blob)
Then, as I put in the final command "fastboot -i 0x0B05 flash recovery twrp.blob" I get the message "error: out of memory" and the fastboot.exe crashed.
What could be causing this? Don't really want to try over again since I have no idea what I might be doing wrong and I really don't want to end up with the hassle of a bricked tablet.
Could it be an issue with the twrp version, and its compatibility with the tablet?
There is no lack of available memory on my computer, and there shouldn't be problems with the tablet's ROM or RAM, as it runs fine except for the obvious problem this tablet has. Previous to unlocking it was wiped and reset to stock 4.2.1 Jelly Bean with the .10 build.
The CMD window looks like this:
"
C:\users\Hbryne.Hbryne-PC>fastboot devices
015d2d431f240415 fastboot
C:\users\Hbryne.Hbryne-PC>cd c:\android-adb
c:\android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
error: out of memory
"
Thanks in advance for any helpful reply!
Click to expand...
Click to collapse
It looks as if you ran the 'fastboot devices' command from a different directory than 'fastboot -i 0x0B05....'
You cd'd into c:\android-adb
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
berndblb said:
It looks as if you ran the 'fastboot devices' command from a different directory than 'fastboot -i 0x0B05....'
You cd'd into c:\android-adb
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
Click to expand...
Click to collapse
Ah, could that have caused it? Figured the connection check could be done from anywhere - maybe that's what triggered the error. Tried again - although now without the check since I know it's connected and recognized - and it worked :laugh:
Thanks!
berndblb said:
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
Click to expand...
Click to collapse
Not true if fastboot is properly installed in a directory that is in the PATH.
_that said:
Not true if fastboot is properly installed in a directory that is in the PATH.
Click to expand...
Click to collapse
True - but very few do...
Sent from my XT894 using Tapatalk
need help
hi im new here
i have alot of problems need help guys
first i was in build ww6.5.0 and was in root yesterday asus push new update in ota i download it and when my device restart to start setup it stop
and get erorr when it bootup gave me this (your device is recoverd to the original configuration) then i delete root (frome super user) and download the update again
same prob
sec idownload the raw image frome asus offcial site ww6.5.0 and my device freez after boot to setup the image and i force it to shutdown after that i can't make factory reset
saying to me E:unable to write /cashe/recovery/command file
and i have no root now
today i downoade the new image UL-K00E-WW-6.6.1.0-user.zip it start fine and copy fiels but got errors too
:Eunable to rename file /cashe/update.zip: cross-device linkE:unable to write file
E:unable to write file: /cashe/update.zip
E:update flash failed
flash failed
fail(flash_cmds error!)
Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)
photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'
So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.
Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.
Oh and that android is stock recovery
U fixed it?
So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.
I've managed to compile 5.1.1 aosp,
here is my problem, fastboot doesn't seem to recognize the command i'm typing in '-S 256M' as stated on the sony site.
If i try and flash them the normal way, for example "fastboot flash system system.img"
it doesn't flash like this, i have tried on linux and windows.
I've attached screenshots to show my problem.
Edit- I should of said first, I can flash boot, recovery and userdata the normal way, but system.img hangs. Fastboot won't let me use the command listed on the sony site when flashing any of the partitions.
My compiled system.img seems fine and I can view and extract the files so I don't think it's corrupted.
issue '-S 265M' after 'flash'..!!!
SO it should be 'fastboot flash -S 265M system system.img'
And you need to specify memory breakdown for the system image only, as it has a massive size, for the rest skip using '-S 265M'
P.S.: You certainly seem to be new at Android compilation.. I would advice you to try checking other forums first... checking out what works and what doesn't before experimenting! Just saying!
Cheers
Okay so I recognize if I had more money I could pay for home internet. But I don't so I'm here with a budget phone, less than ideal tech skills, and can't seem to figure out how to root.
I've borrowed multiple windows 10 computers all the same result.
I've installed the latest Adb drivers from multiple sources. Re-installed drivers. Uninstalled drivers to no avail
I have my bootloader unlocked. I downloaded the latest firmware. I extracted it and patched the boot.img.
whenever I type fastboot flash boot magisk_patched.img this is the result
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
when in fastboot mode i see on my phone
device state: unlocked
boot slot:b
Hoping someone can help Life is frustrating without internet.
Jmcarls20 said:
Okay so I recognize if I had more money I could pay for home internet. But I don't so I'm here with a budget phone, less than ideal tech skills, and can't seem to figure out how to root.
I've borrowed multiple windows 10 computers all the same result.
I've installed the latest Adb drivers from multiple sources. Re-installed drivers. Uninstalled drivers to no avail
I have my bootloader unlocked. I downloaded the latest firmware. I extracted it and patched the boot.img.
whenever I type fastboot flash boot magisk_patched.img this is the result
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
when in fastboot mode i see on my phone
device state: unlocked
boot slot:b
Hoping someone can help Life is frustrating without internet.
Click to expand...
Click to collapse
Just a tip, if you're in dire need of a computer, I'd recommend a raspberry pi. It's really handy for your situation. I also don't have home internet and was using purely a Pi for a fair while, it's definitely enough for adb/fastboot stuffs among other things.
Now, onto your issue. Have you tried specifying the boot slot? Normally you shouldn't have to specify the slot but in your case you may have to.
You can try running the command
Code:
fastboot flash boot_b magisk_patched.img
Also, verify that the magisk_patched.img is in the directory you started the terminal/PowerShell window in with the adb executable.
Sent from my Pixel 3a XL using XDA Labs
can you flash anything else in fastboot? or are you only trying to flash the patched magisk image?
I've attached the latest platform tools from Google.
Unzip this folder to the root of your C:/ so it looks like this: C:/adb
Put your magisk_patched.img in the folder then shift+right click anywhere in the folder and "open command prompt here".
With your phone in bootloader mode, at the prompt type: fastboot flash boot magisk_patched.img
I've just done this to check and mine worked first time . Let me know how you get on .
Is the modified magisk file in the same directory as the SDK tools?
I do not recommend that you start using "boot partition" specific commands. You should not have to specify which boot partition to write to. If it's not working that is an indication of a larger issue that needs to be resolved. I've seen plenty of people make things worse when they start using boot partition specific commands.
Wow thank you for the support. I got it to flash by boot_b but then I tried to reboot and the touch screen didn't work so I reflashed the original boot.img and then redid the boot file today and will try it tonight. Will keep everyone posted and will re try other solutions tonight. Going to have to look into raspberry pi to that sounds like a nice project to try
Hey, i messed up my phone by installing something via magisk. Now im trying to install a new rom.
When i open the phone (lenovo p2a42), i get encryption error. For able to fix that problem i have to use "fastboot format userdata" command but i get raw file system error. How can i fix this? Disk manager doesn't see the phone.
Code:
adb reboot bootloader
error: no devices/emulators found
fastboot devices
ZY223TNMLC fastboot
fastboot format userdata
(bootloader) has-slot:userdata: not found
fastboot: error: Formatting is not supported for file system with type 'raw'.
edit ok i figure it out. power button, adv setting, recovery than continued to next step, there is no need to format
Jhumsmt said:
continued to next step
Click to expand...
Click to collapse
You mean continue to regular boot or continue to recovery?