i took the 8mb boot.img from the nandroid backup/thread, renamed it to .bin, opened with a hex editor, deleted everything after 2cffff (to make correct size), saved as boot.img and flashed. then updated via recovery. cheers.
Code:
fastboot flash boot test_boot.img
edit: uploaded to my host as well: http://mycarbl0ws.com/test_boot.rar
What do u mean u updated via recovery?
Sent from my Nexus S
k0mpresd said:
i took the 8mb boot.img from the nandroid backup/thread, renamed it to .bin, opened with a hex editor, deleted everything after 2cffff (to make correct size), saved as boot.img and flashed. then updated via recovery. cheers.
Code:
fastboot flash boot test_boot.img
Click to expand...
Click to collapse
nice. testing now
plmiller0905 said:
What do u mean u updated via recovery?
Nevermind..I got it..stupid question
Sent from my Nexus S
Click to expand...
Click to collapse
Nevermind..I got it..stupid question
Sent from my Nexus S
Thanks! I just flashed it, and updated w/ CWR. worked fine, at 2.3.1 now
Luxferro said:
Thanks! I just flashed it, and updated w/ CWR. worked fine, at 2.3.1 now
Click to expand...
Click to collapse
hey when you downloaded the file did you rename the file from .rar to .img to flash???
Does this boot img come with root?
Sent from my Nexus S using Tapatalk
brian6685 said:
Does this boot img come with root?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
no. this is stock.
JDMSirEK4 said:
hey when you downloaded the file did you rename the file from .rar to .img to flash???
Click to expand...
Click to collapse
an .rar is a compressed file. unrar the file to get the .img
Do u lose clockwork recovery when u reboot? That's the problem I'm having updating to 2.3.1
breaks wifi for me
How do I flash the img? Do I use adb and if so what's the adb commands?
After I flash this, i just go into rom manager and download/install the update and that's it?
Will i lose root by flashing this?
Sent from my Nexus S
k0mpresd said:
no. this is stock.
Click to expand...
Click to collapse
Okay thanks
Sent from my Nexus S using Tapatalk
Can somebody HELP! What I'm I doing wrong that I can't flash the boot.img!!! I'
m getting an error everytime.
This is what i'm typing in "FASTBOOT":
c:\android-sdk-windows\platform-tools>fastboot flash boot test_boot.img
error: cannot load 'test_boot.img'
Silrocco said:
Can somebody HELP! What I'm I doing wrong that I can't flash the boot.img!!! I'
m getting an error everytime.
This is what i'm typing in "FASTBOOT":
c:\android-sdk-windows\platform-tools>fastboot flash boot test_boot.img
error: cannot load 'test_boot.img'
Click to expand...
Click to collapse
test_boot.img should be in the folder, c:\android-sdk-windows\platform-tools\
since that is where you are running flashboot from
graemegb said:
breaks wifi for me
Click to expand...
Click to collapse
looks like installing a rooted img breaks wifi. i did the superboot/paulobrian method then installed the voodoo ext 4 kernel, then wifi was broken.
i reflashed my boot.img and re-updated via recovery and i have wifi back.
vroomr4 said:
test_boot.img should be in the folder, c:\android-sdk-windows\platform-tools\
since that is where you are running flashboot from
Click to expand...
Click to collapse
Thanks for the help...it worked.
worked!!!....so can we gain root access back or we just got to hang tight?
the flash worked but I can't update, it says file_getprop: failed to stat "system/build.prop" No such file or directory.
Error in sdcard/update.zip (status 7)
JDMSirEK4 said:
worked!!!....so can we gain root access back or we just got to hang tight?
Click to expand...
Click to collapse
heres how to get root back:
download the superboot/paulobrian method.
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
Related
-build koush’s CWM 5.5.0.4 from CyanogenMod’s repo
-use latest ICS kernel
http://droidbasement.com/db-blog
Awesome!!!!
SGT 10.1 uplink initiative
Will this work on the I/O version?
Sent from my HTC Vision using Tapatalk
Yes
......
pershoot said:
Yes
......
Click to expand...
Click to collapse
Nice
Sent from my HTC Vision using Tapatalk
Works great, looks like I'm the only one to try it lol.
Sent from my HTC Vision using Tapatalk
What are the advantages of flashing a new recovery when you can already flash any zip using the default one?
Backup and restoring your entire system
Sent from my HTC Vision using Tapatalk
The ability to flash round via rom manager is also nice
Sent from my GT-I9100 using Tapatalk
fixing one issue.
will refresh later.
trying to wait for the update... prob just flash back to back. what is the issue you are fixing? Thanks for doing this.
galaxy tab 10.1 - clockwork mod recovery - refreshed.
jaskru said:
trying to wait for the update... prob just flash back to back. what is the issue you are fixing? Thanks for doing this.
Click to expand...
Click to collapse
nandroid backups.
fixed. refreshed. filename has not changed (its labelled 0521).
I'm getting a cannot determine image filename error. Any tips??
thepro8 said:
I'm getting a cannot determine image filename error. Any tips??
Click to expand...
Click to collapse
show me what you are doing.
pershoot said:
show me what you are doing.
Click to expand...
Click to collapse
I just rooted my device. Rebooted it.
Downloaded the clockwork recovery file, unzipped it, the .img file is in my downloads folder (did not change the name)
(in cmd window)
cd downloads
fastboot flash recovery recovery-cwm_3.1.0.1-sam-tab-10.1-052111.img
(I get back)
error: cannot load 'recovery-cwm_2.1.0.1-sam-tab-10.1-052111.img'
thepro8 said:
I just rooted my device. Rebooted it.
Downloaded the clockwork recovery file, unzipped it, the .img file is in my downloads folder (did not change the name)
(in cmd window)
cd downloads
fastboot flash recovery recovery-cwm_3.1.0.1-sam-tab-10.1-052111.img
(I get back)
error: cannot load 'recovery-cwm_2.1.0.1-sam-tab-10.1-052111.img'
Click to expand...
Click to collapse
check the filename.
it is not recovery-cwm_3.1.0.1-sam-tab-10.1-052111.img when you unpack it.
ensure you have a working fastboot
you should fastboot boot it first prior to flashing/replacing.
you do not need to root your device to use this. if you are using this on the 'v', then you must unlock your bootloader prior.
pershoot said:
ensure you have a working fastboot
Click to expand...
Click to collapse
I think this may be the problem because if try a "fastboot reboot" command I just get a waiting for device and nothing else.
hmm...how do i fix that
thepro8 said:
I think this may be the problem because if try a "fastboot reboot" command I just get a waiting for device and nothing else.
hmm...how do i fix that
Click to expand...
Click to collapse
check the stickies in the 'v' forum.
Looks like i fixed it. i had to get my tablet into fastboot mode and then plug it in. then it detected my device and i was able to flash it.
In case accidentally goof up something, here is a stock lollipop system image that can be flashed in fastboot.
To flash it, attach phone to computer, open terminal and issue:
Code:
fastboot flash system system.img
Ensuring that the path to the file is correct that is.
This only flashes the system image, you can get stock boot and recovery from intersect's other thread.
Download: http://d-h.st/nDsQ
saved my @SS !!! Thanks
Merry Christmas!
thanks!
kashortiexda said:
saved my @SS !!! Thanks
Click to expand...
Click to collapse
+2
Juste In case of, here is an how to guide : http://forum.xda-developers.com/g-watch-r/development/emergency-guide-how-to-blank-regenerate-t2984678
hi.
what are the benefits of this rom? is su enabled? can we make vibrations stronger as in 4.4 ?
thnx
tonu42 said:
In case accidentally goof up something, here is a stock lollipop system image that can be flashed in fastboot.
To flash it, attach phone to computer, open terminal and issue:
Code:
fastboot flash system system.img
Ensuring that the path to the file is correct that is.
This only flashes the system image, you can get stock boot and recovery from intersect's other thread.
Download: http://d-h.st/nDsQ
Click to expand...
Click to collapse
thanks, can i flash it without install root and recorvery before ??
ngocxuyen said:
thanks, can i flash it without install root and recorvery before ??
Click to expand...
Click to collapse
Just need to use fastboot. No root or recovery required.
Is Flickering problem gone with this rom ?
Sent from my SM-N910F using Tapatalk 2
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.
faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img
rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.
Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*
rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea
faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).
The only .zip I can find already has a modified boot.img that is rooted. I'm looking for a bone stock one so that I can apply the H21120x OTA via TWRP. (I guess I Could just write out the boot.img update from the updater-script).
Anyone have a copy of this from their device or a way to get it from a KDZ?
pizzaboy192 said:
The only .zip I can find already has a modified boot.img that is rooted. I'm looking for a bone stock one so that I can apply the H21120x OTA via TWRP. (I guess I Could just write out the boot.img update from the updater-script).
Anyone have a copy of this from their device or a way to get it from a KDZ?
Click to expand...
Click to collapse
i think you can using ext2explore-2.2.71 you can then get boot.
raptorddd said:
i think you can using ext2explore-2.2.71 you can then get boot.
Click to expand...
Click to collapse
That worked!
I'd also recommend not doing it the way I did (modifying the update.zip and flashing stock boot.img) it seems to have broken Bluetooth.
raptorddd said:
i think you can using ext2explore-2.2.71 you can then get boot.
Click to expand...
Click to collapse
I was able to get a H81120V boot.img extracted from the kdz, but it looks like flashing the update.zip through TWRP breaks bluetooth.
pizzaboy192 said:
I was able to get a H81120V boot.img extracted from the kdz, but it looks like flashing the update.zip through TWRP breaks bluetooth.
Click to expand...
Click to collapse
sorry i just extract and flash ive never modified boot.
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
nebkas said:
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
Click to expand...
Click to collapse
which one? could u please link to that tool or share here your using?
an-_-dro said:
which one? could u please link to that tool or share here your using?
Click to expand...
Click to collapse
I used that one. Just drop off the boot.img.lz4 on the .exe file.
nebkas said:
I used that one. Just drop off the boot.img.lz4 on the .exe file.
Click to expand...
Click to collapse
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
an-_-dro said:
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
Click to expand...
Click to collapse
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
nebkas said:
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
Click to expand...
Click to collapse
maybe 4 or 5 attempts with different patched img but i never make it hahaha of course i also flashed complete downloaded firmware after and wait 7 days between each attempt.
I struggled a lot too yesterday(got my device yesterday ). I used also this one to repack the .img and flashed it with the odin version in the bin directory.
7zip is enough to wrap img file to tar
an-_-dro said:
7zip is enough to wrap img file to tar
Click to expand...
Click to collapse
yes, maybe. But who knows what all the apps are doing. that file makes it to a tar.md5.
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
pr1jker said:
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
Click to expand...
Click to collapse
Sure, but there wasn't any twrp working when I started the Thread
Hello. I am having an issue getting my oem unlock option back. I have followed every tutorial that I could find trying to get rmm back to normal status and have had my a600t1 on for 39 days nonstop. If anyone could give advice or just point me in the right direction I would greatly appreciate it. I'm at a loss. Thanks in advance for any help
guess maybe nobody can help with my issue. i dont know about you all but its polite to answer even if the answer is no.
Just share I have rooted my Samsung Galaxy A6 2018 SM-A600G Android 9 Pie with Magiskm you can watch this video https://youtu.be/1y1p7-Hzm_o
for rooting it, I have to install Magisk twice, one for prevent boot loop after install TWRP and second for rooting after install MagiskManager.
I have a problem with root. I can't set fingerprint because the System crash. After crash i have to install over again. I have notice that twrp recovery have an error when i go in internal storage It have 0mb and i must format
SubGenius said:
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Click to expand...
Click to collapse
did you have boot.img for this devise but for 9.0 thx