Back to Stock (4.1.2 image) and re-root project - Help needed - Samsung Galaxy Nexus

Hello again.
After having ROMed and MODing to my liking, I decided to go back to stock since the 4.1.2 is up for my GN version (maguro).No other partition has been flashed (radio, kernel, etc).
My goal is to get into a stock state using 4.1.2 images and be unrooted.
I am thinking of booting into fastboot then:
fastboot flash all yakju-jzo54k-factory-92ff9457.tgz
I guess that command should:
- flash everything inside the .tgz
- install stock recovery image
- unroot the phone (?)
but wouldn't clear my data and apps I guess.So afterwards I could either:
- fastboot erase userdata
- lock and unlock the bootloader
The goal is to erase all apps and /sdcard parition.Right or wrong?
After I am set up I would like to root the phone but doing it manually and not via CWM .zip installation.
Is there a guide somewhere explaining what needs to be done for rooting cause searching didn't help much...
Thanks in advance.

The GNex toolkit is your friend....
http://forum.xda-developers.com/showthread.php?t=1392310
Download it, connect to phone to PC and follow the prompts. I recently did the same thing (I'm on VZW) completely unrooted and back to stock when VZW released the 4.1 update. Used it for a week or two and came back to CM10 Nightlies. Used the toolkit and re-rooted and what not....
I would recommend donating and getting the auto update feature activated. The link above includes the most recent released download, but it was actually a ways behind if you have the auto update feature active. The dev does not require a certain amount donated, so I felt $15 was plenty.
(Just checked the download link is 7.8 and the auto update brings you up to 8.2)

TR-909 said:
Hello again.
After having ROMed and MODing to my liking, I decided to go back to stock since the 4.1.2 is up for my GN version (maguro).No other partition has been flashed (radio, kernel, etc).
My goal is to get into a stock state using 4.1.2 images and be unrooted.
I am thinking of booting into fastboot then:
fastboot flash all yakju-jzo54k-factory-92ff9457.tgz
I guess that command should:
- flash everything inside the .tgz
- install stock recovery image
- unroot the phone (?)
but wouldn't clear my data and apps I guess.So afterwards I could either:
- fastboot erase userdata
- lock and unlock the bootloader
The goal is to erase all apps and /sdcard parition.Right or wrong?
After I am set up I would like to root the phone but doing it manually and not via CWM .zip installation.
Is there a guide somewhere explaining what needs to be done for rooting cause searching didn't help much...
Thanks in advance.
Click to expand...
Click to collapse
OK, let's get started.
- extract yakju-jzo54k-factory-92ff9457.tgz (tgz means it's a tar file, further compressed with gzip), in the end you'll see:
valhalla% ls -ltch gimages/yakju-jzo54k
total 246M
-rwxr-xr-x 1 bk201 users 831 Oct 13 10:47 flash-all.sh
-rw-r--r-- 1 bk201 users 2.3M Oct 13 10:46 bootloader-maguro-primelc03.img
-rw-r--r-- 1 bk201 users 232M Oct 13 10:46 image-yakju-jzo54k.zip
-rw-r--r-- 1 bk201 users 13M Oct 13 10:46 radio-maguro-i9250xxlf1.img
-rw-r--r-- 1 bk201 users 789 Oct 13 10:46 flash-base.sh
Click to expand...
Click to collapse
- edit flash-all.sh, which contains:
Code:
fastboot flash bootloader bootloader-maguro-primelc03.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-maguro-i9250xxlf1.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-yakju-jzo54k.zip
from here, we will flash bootloader, radio, and update-image, but to do it manually, first we need to extract image-yakju-jzo54k.zip.
valhalla% unzip -l gimages/yakju-jzo54k/image-yakju-jzo54k.zip
Archive: gimages/yakju-jzo54k/image-yakju-jzo54k.zip
Length Date Time Name
--------- --------- ----- ----
4472832 2009-01-01 00:00 boot.img
4823040 2009-01-01 00:00 recovery.img
410365584 2009-01-01 00:00 system.img
140856312 2012-10-03 22:09 userdata.img
93 2012-10-02 15:03 android-info.txt
--------- -------
Click to expand...
Click to collapse
- last step, all the files in the same folder (i'm assuming you have fastboot in your path and device in bootloader mode, connected to the pc), enter the following commands:
Code:
1) fastboot flash bootloader bootloader-maguro-primelc03.img
2) fastboot reboot-bootloader
(..device will reboot into bootloader, obviously wait for bootloader screen to come up again)
3) (optional but recommended) fastboot flash radio radio-maguro-i9250xxlf1.img
4) fastboot reboot-bootloader
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) fastboot flash system system.img
8) (will wipe /data/media; optional) fastboot flash userdata userdata.img
TR-909 said:
The goal is to erase all apps and /sdcard parition.Right or wrong?
Click to expand...
Click to collapse
It's best to fresh start yes, but userdata is just /data/media.
also, with this process, no need to unroot. /system will be wiped.
if you want to root manually, and i'm pulling this from my head, you just need to push su binary to /system/xbin and chmod 0755 06755 it, and push supersu.apk to /system/app and chmod 0644 it. attention, this will either require the use of an exploit (for example, the one available to root without unlocking bl), or
Code:
fastboot boot cwm_or_twrp.img
....remount system rw (we have temp root because of custom recovery)
Code:
mount -o rw /dev/block/platform/omap/omap_hsmmc.0/by-name/system /system
push su binary/supersu.apk to the previously said locations and set permissions (i've checked a flashable zip i got from efrant and it seems it's 06755)
Code:
adb push supersu/system/xbin/su /sytem/xbin/su
adb shell chmod 06755 /system/xbin/su
adb push supersu/system/bin/su /system/bin/su
adb shell chmod 06755 /system/bin/su
adb push supersu/system/app/Superuser.apk /system/app/Superuser.apk
adb shell chmod 0644 /system/app/Superuser.apk
adb reboot
done. someone please post if i missed/got anything wrong. this is i would go about it.
you could just have read this.

Hey bk201doesntexist.
Actually I read the guide of efrant and was questioning myself about fastboot flash all command but I probably haven't understand it well.I am going to proceed and do all steps as you suggest.
Back to work... will report soon.
Thanks.
EDIT: Currently on 4.1.2 updating gapps, whole procedure took less than 3 minutes including reboots! Didn't thoroughly check new update but first I am going to bring back my apps and stuff through TiB.
About Rooting: so basically I should boot temporarily on CWM and Adb do the root thingie.Ok let me look into it...

Related

help! deleted recovery.img

just wondering if anyone can help me out here, i was trying to flash the cyanogen hero recovery image to my phone using fastboot so i erased my stock recovery image, only to get the message "remote: signature verify fail" so im now stuck with no recovery image and dont know how to get it back, can anyone help me out please?
ok so i managed to mount my system as read write in fastboot and put the recovery.img from the wwe version in to system which has gave me my recovery back but when i boot it just stays on the hero screen and says fastboot usb at the top if i have it plugged into my pc. i have no idea how to reset the original files and i didnt back up, can anyone help me pleas?
Well after trying for hours to fix this, I give up. I can't install the system.img from wwe rom posted on here it says verify failed or something similar so I stupidly tried to flash the magic 32a heroski port hoping it would work and still nothing. Is there anyway someone could post there nandroid backup file and help me flash it to see if that works? Or should I just give up. I'm really stuck now lol
you can't flash anything from fastboot because the images need to be signed.
what version of hero do you have?
if you have the wwe hero(it's not needed ) i can send you (later, now i'm at work) my nandroid backup (system,boot,recovery, splash...) so you can restore them
I have the orange hero. I used fastboot to load cyanogens recovery image then flashed the heroski rom hoping it might work lol so I ended up using fastboot to erase system. Question is do you think your nandroid backup would work? I sure hope so it would be a great help!!! Thanks.
i have the unlocked wwe hero. i'm uploading now the system, boot and recovery to rapidshare . it'll be up in a couple of minutes. if you find a orange hero backup you can restore in the same way ;-)
restoring hero wwe
download the backup from(it's better if you verify the md5):
http://rapidshare.com/files/263636068/bkp.rar.html
MD5: BEAE167BCBB1FF6D3D2701FB64604203
Put the contents on sdcard (i'm assuming that you put the images in a folder named bkp on the sdcard)
so:
download the recovery from here: http://rapidshare.com/files/262621147/cm-hero-recovery.img.zip and extract it
put your phone in fastboot mode (with the phone off, press the back key then turn the phone on).
then:
boot with the downloaded recovery
Code:
fastboot boot cm-hero-recovery.img
0) mount the partitions
Code:
adb shell mount /system
adb shell mount /sdcard
1) do a wipe
select the wipe option from the recovery menu
2) restore boot
Code:
adb shell flash_image boot /sdcard/bkp/boot.img
3) restore recovery
Code:
adb shell flash_image recovery /sdcard/bkp/recovery.img
4)restore system
Code:
adb shell
cd /system
rm -rf * (ignore the errors)
unyaffs /sdcard/bkp/system.img
5) unmount the partitions
Code:
umount /system
6) reboot
Code:
reboot
hope it helps
Ok thanks. Have to wait 4 hours to try it as I'm in work lol, what is an md5 for, just out of curiosity?
A MD5sum is a checksum to verifiy that your downloaded file isn't corrupt.
maxisma said:
A MD5sum is a checksum to verifiy that your downloaded file isn't corrupt.
Click to expand...
Click to collapse
Ok dude makes sense thanks.
thanks
enlightener said:
download the backup from(it's better if you verify the md5):
http://rapidshare.com/files/263636068/bkp.rar.html
MD5: BEAE167BCBB1FF6D3D2701FB64604203
Put the contents on sdcard (i'm assuming that you put the images in a folder named bkp on the sdcard)
so:
download the recovery from here: http://rapidshare.com/files/262621147/cm-hero-recovery.img.zip and extract it
put your phone in fastboot mode (with the phone off, press the back key then turn the phone on).
then:
boot with the downloaded recovery
Code:
fastboot boot cm-hero-recovery.img
0) mount the partitions
Code:
adb shell mount /system
adb shell mount /sdcard
1) do a wipe
select the wipe option from the recovery menu
2) restore boot
Code:
adb shell flash_image boot /sdcard/bkp/boot.img
3) restore recovery
Code:
adb shell flash_image recovery /sdcard/bkp/recovery.img
4)restore system
Code:
adb shell
cd /system
rm -rf * (ignore the errors)
unyaffs /sdcard/bkp/system.img
5) unmount the partitions
Code:
umount /system
6) reboot
Code:
reboot
hope it helps
Click to expand...
Click to collapse
ok so i finally got time to fix my phone and just did what you said and can now happily say it worked. thanks enlightener you enlightened me lol. in future i will refrain from doing random terminal stuff without researching first lol.
Bad new : My hero is out of service area
Hello,
Sorry for my english, i'm french
I made a big mistake in my files system ... A too long story
My Hero :
HBOOT-1?76.0004
Radio-6.35.04.25
July, 3 2009
Well, now, my htc hero do not work 'first page, out of service area"... I would like to make your post, but i had error :
First, fastboot Ok, Adb shell mount system and sdcard ok, wipe ok
Second, when i do this code" adb shell flash_image boot /sdcard/bkp/boot.img", my hero "said" : "header is the same, note flashing boot". Same thing for restore recovery
Can you help me ?
pitou21 said:
Hello,
Sorry for my english, i'm french
I made a big mistake in my files system ... A too long story
My Hero :
HBOOT-1?76.0004
Radio-6.35.04.25
July, 3 2009
Well, now, my htc hero do not work 'first page, out of service area"... I would like to make your post, but i had error :
First, fastboot Ok, Adb shell mount system and sdcard ok, wipe ok
Second, when i do this code" adb shell flash_image boot /sdcard/bkp/boot.img", my hero "said" : "header is the same, note flashing boot". Same thing for restore recovery
Can you help me ?
Click to expand...
Click to collapse
in this case, you don't have to restore boot or recovery because they are the same as the images posted here.
proceed with system
Ok thanks, now it's goog !

Howto apply manually update to 4.0.4 with encrypted flash and minor changes

OK i'm posting this since it was a bit complex and i think others could benefit.
I was on 4.0.2 stock HSPA (yakju-icl53f). But i had made some minor changes, and worse, had encrypted the flash. How to update to 4.0.4 without a wipe? Turns out it is possible.
First, get CWM and 4.0.4 image.
Clockworkmod from here.
OTA image from 4.0.2 to 4.0.4 from here.
Steps needed:
1. adb reboot bootloader
2. fastboot cwm.img
3. adb shell
4. mount -t tmpfs -o size=330M,mode=0777 tmpfs /sdcard
5. adb push 7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip /sdcard/update.zip
6. unzip 7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip META-INF/com/google/android/updater-script
7. unzip 7f97fbc19417.signed-yakju-IMM76D-from-ICL53F.7f97fbc1.zip META-INF/com/google/android/update-binary
8. adb push META-INF/com/google/android/updater-script /sdcard/
9. adb push META-INF/com/google/android/update-binary /sdcard/
10. Fix all the changes you made in the past <more below>. You can try the below steps and just see which assert fail, and then fix them one by one
11. adb shell
12. cd /sdcard/
13. chmod a+rx *
14. ./update-binary 2 stdout update.zip
15. reboot and enjoy.
The changes i had made were to build.prop (adding ro.config.vc_call_vol_steps=10 from volume+) and to remove GenieWidget.apk via TitaniumBackup.
To fix these, i got the 4.0.2 stock image from here.
1. tar zxvf yakju-icl53f-factory-89fccaac.tgz
2. cd yakju-icl53f
3. unzip image-yakju-icl53f.zip
4. Get the ext4_utils file from here. Build it.
5. run simg2img system.img x.img
6. mkdir ./x; sudo mount -o loop -t ext4 ./x.img x
7. adb push x/app/GenieWidget.apk /system/app/
8. adb push x/app/GenieWidget.odex /system/app/
9. adb push x/build.prop /system/
[i just kept running the update-binary 2 stdout update.zip and watching the assert until i knew what all i had changed].
After all this, i rebooted, and it worked. Despite my being encrypted. Despite my changes. Despite my not being eligible for OTA yet. Once i rebooted, i entered my decryption key, it chewed on the upgrade for a bit, and i'm on 4.0.4
Enjoy. The above instructions are for Linux obviously, and may have some minor typos as i did them afterwards.
Thank you for this howto!
Since you are "just updating" I assume you lost root?
Did the boot duration change? With crypted SGN 4.0.2 it takes an eternity and a half to boot.
yes, lost root, had to re-apply (you can use the above instructions but put the super-user zip in for cwm).
no change in boot time
Mmm, you can also do a 'mount -a; chmod 4755 /system/bin/su' if you previously had root, @ step 3 (after rebooting w/ all the changes, redo 1/2/3).
For interest (to open an old thread), this worked to move to Jelly Bean as well. I took the clockworkmod version of the JB from here.
I used the same basic steps as above, but w/ the change of:
1. make ram disk (using 390M instead of 330M)
2. unzip jb-takju.zip (on pc)
3. adb push boot.img /sdcard/
4. adb shell; cat /sdcard/boot.img > /dev/block/platform/omap/omap_hsmmc.0/by-name/boot
5. adb push system.tar /sdcard
6. adb shell; mount /system; cd /system; rm -rf *; cd /; tar xvf /sdcard/system
7. reboot. enjoy.
This kept all my settings, apps, everything... its seamless.

Help me how to root Official 4.0.4 IMM76D

I just upgraded my GNex GSM yesterday.
It's now smoother than ever before...
But one thing is I wanna get root access on my GNex
GSM 4.0.4 IMM76D.
Is there any CF-Root or something available now...?
here it comes in 3...2....1........
.4 is unrootable. Would've known if you searched.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
zeyarwynntun said:
I just upgraded my GNex GSM yesterday.
It's now smoother than ever before...
But one thing is I wanna get root access on my GNex
GSM 4.0.4 IMM76D.
Is there any CF-Root or something available now...?
Click to expand...
Click to collapse
This question sounds more like: I just lost my glassess and I don't know how to read!
http://forum.xda-developers.com/showthread.php?t=1382163
Try a search, You might find one of the 20ish threads that have an answer in it on how to root your Gnex.
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
@rbiter said:
.4 is unrootable. Would've known if you searched.
--------+++--------
iphone. helping computer illiteracy become popular since 2007.
Click to expand...
Click to collapse
10/char
Galaxy Nexus Toolkit v5.6
Oh, yes, I've lost my glasses...
I just have my GNex rooted with Galaxy Nexus Toolkit v5.6
zeyarwynntun said:
Oh, yes, I've lost my glasses...
I just have my GNex rooted with Galaxy Nexus Toolkit v5.6
Click to expand...
Click to collapse
Is it possible to root without using cwm?
I'm not interested in flashing non stock images.
sblantipodi said:
Is it possible to root without using cwm?
I'm not interested in flashing non stock images.
Click to expand...
Click to collapse
No, it is not possible to root IMM76D without using CWM.
That said, you DO NOT have to flash CWM to be able to use it...
EDIT: j.go (who posted below me) is right. You can root by booting an insecure kernel (which by the way is what CWM is), and copying the two files over using ADB (which is essentially what CWM does, but much easier).
efrant said:
No, it is not possible to root IMM76D without using CWM.
That said, you DO NOT have to flash CWM to be able to use it...
Click to expand...
Click to collapse
You can root without CWM. Fastboot boot with unsecure boot image. Adb push su and superuser.apk. Reboot. Congratulations, you are rooted.
j.go said:
You can root without CWM. Fastboot boot with unsecure boot image. Adb push su and superuser.apk. Reboot. Congratulations, you are rooted.
Click to expand...
Click to collapse
I don't understood, can you make a step by step guide please?
I want to root my phone leaving as much as stock items as possible.
How to root ANY build, on a GN with an unlocked bootloader
Note: There is currently no way to root IMM76D (i.e., 4.0.4) without an unlocked bootloader. The following method is for devices with unlocked bootloaders.
Method 1
1) Download CWM from here to your computer: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img.
2) Download the attachments from here to your computer: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Download this to your /sdcard on your device: http://www.box.com/s/jvcf196j7x8f8vrc9cyt
4) Extract all the files into one directory, and put cwm.img in there
5) Restart your device in fastboot mode and plug into computer
6) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
7) Wait for it to boot
8) Navigate the menus. There is an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
9) Reboot. Done.
Method 2 (more manual)
1) Download CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img If you are having problems, download the attachment from here and use it instead of CWM.
2) Download the attachments from here: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Extract all the files into one directory, and put cwm.img in there
4) Restart your device in fastboot mode and plug into computer
5) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
6) Wait for it to boot
7) In the command prompt, type the following:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
8) Done.
Note: if you are having problems mounting /system in CWM, try doing it in CWM itself (on device via the menu), instead of typing in the command.
EDIT: Added title and note.
efrant said:
1) Download CWM from here: http://forum.xda-developers.com/showthread.php?t=1357642 and rename it cwm.img
2) Download the attachments from here: http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
3) Extract all the files into one directory, and put cwm.img in there
4) Restart your device in fastboot mode and plug into computer
5) Open a command prompt in the directory mentioned above and type: fastboot boot cwm.img
6) Wait for it to boot
7) In the command prompt, type the following:
adb push su /data/local/tmp/su
adb push Superuser.apk /data/local/tmp/Superuser.apk
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
8) Done.
Click to expand...
Click to collapse
this will give me the root access on a stock 4.0.4 phone?
in the thread at point 2) is wrote that this does not work on 4.0.4.
sblantipodi said:
this will give me the root access on a stock 4.0.4 phone?
Click to expand...
Click to collapse
Yes.
sblantipodi said:
in the thread at point 2) is wrote that this does not work on 4.0.4.
Click to expand...
Click to collapse
That is why you are not following the directions in that thread. You are following the directions in this thread, right?
efrant said:
Yes.
That is why you are not following the directions in that thread. You are following the directions in this thread, right?
Click to expand...
Click to collapse
lol... great
do you think that this way of rooting will create problem in future OTA notifications?
sblantipodi said:
lol... great
do you think that this way of rooting will create problem in future OTA notifications?
Click to expand...
Click to collapse
No, it will not. Rooting by ANY method does not affect OTAs...
P.S. There is a slightly easier method that I will add to the previous post soon. (I wanted to put in the fully manual method so you can see what is happening.)
Another question, I am an app developer so adb and fastboot are in my default path from the original SDK.
Can I use my ADB and FastBoot from my SDK?
sblantipodi said:
Another question, I am an app developer so adb and fastboot are in my default path from the original SDK.
Can I use my ADB and FastBoot from my SDK?
Click to expand...
Click to collapse
Yes.
10 char
Hey efrant, if I wanted to remove the Superuser.apk and su files already on the device, could I follow Method 2 and fastboot boot cwm.img then do the following in step 7:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
rm /system/bin/su
rm /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
Then once done, disconnect usb cable and reboot the device?
This would essentially leave me with stock recovery, locked bootloader and no root - correct?
ruffneckc said:
Hey efrant, if I wanted to remove the Superuser.apk and su files already on the device, could I follow Method 2 and fastboot boot cwm.img then do the following in step 7:
adb shell
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
rm /system/bin/su
rm /system/app/Superuser.apk
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
Then once done, disconnect usb cable and reboot the device?
This would essentially leave me with stock recovery, locked bootloader and no root - correct?
Click to expand...
Click to collapse
Is your bootloader locked or unlocked currently? You cannot use fastboot commands if your bootloader is locked.
Assuming that your bootloader is unlocked, your procedure is correct, although you would have to relock you bootloader afterwards by booting into fastboot mode, and typing: fastboot oem lock
However, re-locking is something that I never recommend to anyone.
efrant said:
Is your bootloader locked or unlocked currently? You cannot use fastboot commands if your bootloader is locked.
Assuming that your bootloader is unlocked, your procedure is correct, although you would have to relock you bootloader afterwards by booting into fastboot mode, and typing: fastboot oem lock
However, re-locking is something that I never recommend to anyone.
Click to expand...
Click to collapse
My bootloader is currently locked. Regarding re-locking it, I'm just curious as to why you don't recommend it? Essentially, I want keep the option of getting OTAs and get rid of the "Unsupported Device" message in Google Wallet. I read that the app checks for root by looking for the two files and whether the device release keys are modified.
I really appreciate your help.
i have made a CWM flashable su.
if anyone wants. instead of going through all the mount, and copy process,
you will just need to flash the su from the zip file,
go to play store and install the Superuser.apk and then from that update su to the latest version.
if interested, let me know.

[TUT][DUMP] DUMP Stock ROM (SYSTEM/BOOT/etc) | OneX_SEA_WWE_1.26.707.2_SYSTEM + BOOT

Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB
Hi,
can you tell me how to dump mine? My phone arrives tomorrow.
Thanks in advance...
@anko
Thread updated with guide.
so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.
ck_looi said:
so, is it true that i can simply download the system dump from the link your provide, and flash it via recovery if i want to go back to stock SEA rom?
by the way, i am using a SEA htc one X too.
Click to expand...
Click to collapse
not sure & never try
it was dumped before i unlock my device.
see here if u want unlock & backup ur stock rom including boot image. do nandroid backup after flashing Interim CWM. Then only restorable. (boot .img still hv to flash thru fastboot to restore or use new method by blubbers)
my current stock is 1.26.707.4
will i be able to flash this and then get update to 707.4 OTA? Just want to make sure i got the right stock rom for my one x.
Picked mine up today going to do system dump of mine its on t-mobile software is 126.110.5
Sent from my HTC One X using XDA
monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
Click to expand...
Click to collapse
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?
zenkinz said:
i just dump boot (mmcblk0p4) and system (mmcblk0p12). is that good enough? (maybe recovery partition) I assume i would use fastboot flash to flash this image if I want to revert to stock?
Click to expand...
Click to collapse
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.
monx® said:
Yes but RUU 1.26.707.4 is available (at least for our region). better extract *.img directly.
Click to expand...
Click to collapse
ok thanks.
I've done Paul's procedure to Unlock + Interim CWM + SU, so now I'm rooted with S-On. After which I've done full backup thru interim CWM recovery prior to uninstalling bloatwares and I'm still now on stock ROM.
How different is this backup then? Back to stock?
Sent from my HTC One X using xda premium
Gday, now this looks like it spits out a tar file, I assume this is flashable through fastboot? I'm just trying to put together a fastboot flashable img of my providers stock rom for another user...
Edit, I might be being stupid, but shouldn't adb pick up the stock rom when connected and booted into rom? Put usb connection into usb host mode...
M.
2nd method works great...
monx® said:
Basically u need adb/android SDK before proceed.
[WITH ROOT ACCESS]
[+] Dump/copy boot.img
Code:
Command prompt :
> adb shell
> su
> dd if=/dev/block/mmcblk0p4 of=/sdcard/boot.img
More partition/img availabe to dump. Will update later.
[WITHOUT ROOT ACCESS]
Currently only /system is usable
1) Android SDK (just need adb)
2) Download busybox
3) Command prompt :
> adb push busybox /data/local/busybox
> adb shell
> cd /sdcard/
> chmod 755 /data/local/busybox
> /data/local/busybox tar cvf sysdump.tar /system
4) Ignore tar: error exit delayed from previous errors'. Is done correctly.
----------------------------------------------------------------------
Just finished dumped my semi-virgin One X system partition from SEA WWE stock ROM .
The file would be OneX_SEA_WWE_1.26.707.2_SYSTEM_DUMP.zip 558.3 MB
Click to expand...
Click to collapse
Does this work on other models?
helloansuman said:
2nd method works great...
Click to expand...
Click to collapse
Hi, I was curious if this worked on other models specifically the xperia arc so-01c. I wish to dump a japanese docomo rom that I guess is pretty rare for English websites. Thanks in advance. AJ
I already have my boot.img and what not just need to dump my boot.img-kernel... How to?
2nd method works great on other phone thankx man!
just tell us one more thing that how to dump boot/kernel in the same is it possible or not ??

Pre Rooted PATCHED_BOOT.IMG (10.0.4) for Magisk Root

Original tutorial located at https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307
Hello all. Just providing this file for convenience. All credit goes to original author of the guides. This file is a pre-rooted, magisk patched boot.img for firmware version 10.0.4. Use this boot.img for flashing/booting if you are on version 10.0.4 and want to have root using magisk.
!!!I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE. USE COMMON SINCE AND YOU WILL BE OK!!​
STEP 1 - Put phone into fastboot mode
Code:
adb reboot fastboot
STEP 2 - Boot the patched boot.img. Download here
Code:
fastboot boot patched_boot_10.0.4.img
STEP 3 - Backup current boot.img. Open an adb shell and find which block device contains your boot partition and then using dd, make a copy of it.
Open ADB Shell
Code:
adb shell
then
Code:
su
Find boot partition
Code:
ls -lah /dev/block/bootdevice/by-name | grep -i boot
You will see something like this as output:
boot_a -> /dev/block/sde11
boot_b -> /dev/block/sde38
Make copy of boot partition(s)
Code:
dd if=/dev/sde11 of=/sdcard/boot_backup.img
DO THIS FOR BOTH BOOT PARTITIONS, LABEL ACCORDINGLY. JUST IN CASE!
Backup boot.img file(s) to PC
FROM YOUR PC, OPEN COMMAND PROMPT AND DO FOR BOTH IMAGES.
Code:
adb pull /sdcard/boot_backup.img
STEP 4 - Install magisk manager
Get magisk manager APK from here. Download the app-release.apk and install on phone.
Code:
adb install app-release.apk
STEP 5 - Open magisk manager and select Install -> Direct Install.
After you have completed the above steps, if everything worked correctly, and you followed the steps with common sense, everything should be good to go.
The download link is not working. Do you still have a patched 10.0.4 boot image?

Categories

Resources