Related
Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron
I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.
Was going to ask a dumb question but I figured it out
i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.
jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..
Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?
I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?
I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?
well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.
Hi there,
i got a 6800 with stock (but rooted) ICS running and wanted to try the ZETA 4.0 Rom from the development section - what seems to be a minor task turned into disaster ;-/
I followed the instructions from the message in the development forum:
quote:
Do a Nandroid backup!
Copy the Zeta to your SD
(optional) Wipe Data/factory reset
Wipe Dalvik Cache
Install zip from sd
Reboot
I used CWM to backup all information, (which took like 30 mins and ended in an error message)
and when i clicked on "wipe data/factory reset" in recovery things went seriously wrong ...
it seemed to take a very long time (15`+mins) and then rebooted
I am now stuck at the white/blue glowing samsung logo
I can get back into recovery, but when i try to install the "Zeta Rom V4.0.zip" file from the SD card, i just get a
E: signature verification failed in red lettering ... before that, the package is found/opened/verified
also, the cwm.zip is opening, but acting very weired (cant select with the volume keys
The weired thing to me is that I didnt even install the Zeta package when things got ugly!!! - I just did a data wipe
could some good soul pls help me out ...
thx in advance for your time
Al
Hi dude,
Did you try the download mode? (Powerbutton + vol down.) If this still works, your good.
Just get the .Pit file for your device from www.sammobile.com
Now flash this .Pit file with your pc using Odin. If you don't know how to use Odin, please find the thread for this and.read it to the letter! Whatever you do, DON'T set the function for REPARTITION.. that would be THE END dude. Beware!
I had fckd up my tab too, but the Odin solution works fine. After this you can install a new recovery even with Odin and your good M8
After that your good to go and please, of you want to go custom...try the Paranoid Android or Singha light rom . Both are top working, and with the pimp my rom addon (you will find it :good: ), you won't even think about another flash again.
Just don't panic..Good luck!
Regards,
Axelman
Sent from my GT-P6800 using xda app-developers app
Hi there, and thx for responding ...
I can get into download mode (pwr / vol-)
a few extr problems ... I lost the cable to hook up the 7.7 to a computer (3 children household, dont ask ) ... the only form to get files to the tab is pulling the SD card and manually copy files on it and put it back ...
I located 6800.pit files ... so would I just copy those 6800.pit files to the SD and install them in download mode? - could somebody confirm this?
again, thx for answering
Al
sorry, also - could you point me to the 6800.pit file on sammobile ? .... I seem to be unable to locate it ...
thx!
al128 said:
sorry, also - could you point me to the 6800.pit file on sammobile ? .... I seem to be unable to locate it ...
thx!
Click to expand...
Click to collapse
nevermind ... it seems I found it here on xda ...
http://forum.xda-developers.com/showpost.php?p=27636101&postcount=4
(could you confirm that this is the correct one ¿ ... can this be flashed directy via recovery¿
I also leant that I seemed to have superbricked my 6800 by using the "wipe data/factory reset" option in recovery, which supposedly is a bug in the firmware ...
absolutely not amused !
thx for helping
Hi,
Don't use the recovery anymore... as you said, it gave an error anyway. Get a cable and do it the only right way by using Odin.
The super brick means that also the download mode is corrupted...that's the end of the tab for sure, but you still can use the download mode so you are good.
It's your call, but in my opinion your better off with the official download mode (lucky you to still have it) then using a corrupted recovery.
For your info... I would use the Gtp6800 LQ2 .PIT file. If your tab is a 6800 offcorse .
Goodluck m8
Regards,
Axelman
Sent from my GT-P6800 using xda app-developers app
thx axelman, dont worry - I will do it right ... (well, as good as i can do it)
...getting a cable first thing tomorrow ... I cant afford to lose my tab&phone
cheers, Al
Thread moved to Q & A section, post in the relevant section next time.
al128 said:
thx axelman, dont worry - I will do it right ... (well, as good as i can do it)
...getting a cable first thing tomorrow ... I cant afford to lose my tab&phone
cheers, Al
Click to expand...
Click to collapse
He dude,
Use a download from sammobile. Get an account and download the official firmware there. It is the safest way!
I dont know were you are from, but the first ICS build was the open Austria.. P6800XXLQ1
You could use that version, or get the newer version p6800XXLQ2. But you can get any version you like..
GoodLuck
Regards,
Axelman
Axelman8 said:
He dude,
Use a download from sammobile. Get an account and download the official firmware there. It is the safest way!
I dont know were you are from, but the first ICS build was the open Austria.. P6800XXLQ1
You could use that version, or get the newer version p6800XXLQ2. But you can get any version you like..
GoodLuck
Regards,
Axelman
Click to expand...
Click to collapse
I managed to get all things running as per your advice:
I can connect and flash both the stock austrian rom and stock austrian .pit file (I even get a green "pass" in odin!) ... but I am still in a boot trap. I am pretty sure I have those corrupted blocks in the var. partitions ...
I found the following description here on xda ... but it says to TICK the "repartition" ... so I am kind of confused ...
(snip)
What Do You Need To Fix This
1. Odin and Pit get it Here ---> Odin3 v1.85.rar Pit and CWM Include in Odin.
2. Use this Stock Rom P6800XXLQ1_P6800OXALQ1_ATO. This is Open Austria Stock Rom Get it here ==>> Download and Unzip.
3. USB Connector.
3. All You Have and you a ready to Go.
4. Open Odin
5. Tab to Download Mode (( Start + Down Vol ))
6. Connect USB
7. Make Sure the port com detected.
8. Put the Pit file to PIT. Make Sure the PIT is GT-P6800 PIT for P6800XXLQ1_P6800OXALQ1_ATO.pit
9. On Files PDA Make Sure it's XXLQ1_OXALQ1_ATO.md5
10. Make Sure Tick Re-Partition, Auto Reboot and F. Reset Time
11. If you are Ready. Hit the START.
12. If you are successful Com Port box on the Blue and Green in color after the reset and show a pass.
(/snip)
I am confused ... should i tick it or untick it? ... it seems to automatically tick itself on whenever you add a .pit file - so far i UNticked the repartition option
I guess I need to go the whole "adb" route, but it seems to be way over my head ... I cant even get adb to run (a dos window opens and closes immediately) ... pretty frustrating ... there are 70 pages or so to read ... and while I do understand the whole concept, I cannot do it (operationally) ...
well, insult coming to injury ... I am also looking for a job and need my cel desperately
again, thx to all the folks looking into the matter and lending a hand!
cheers, Al
Go back to stock
al128 said:
I managed to get all things running as per your advice:
I can connect and flash both the stock austrian rom and stock austrian .pit file (I even get a green "pass" in odin!) ... but I am still in a boot trap. I am pretty sure I have those corrupted blocks in the var. partitions ...
I found the following description here on xda ... but it says to TICK the "repartition" ... so I am kind of confused ...
(snip)
What Do You Need To Fix This
1. Odin and Pit get it Here ---> Odin3 v1.85.rar Pit and CWM Include in Odin.
2. Use this Stock Rom P6800XXLQ1_P6800OXALQ1_ATO. This is Open Austria Stock Rom Get it here ==>> Download and Unzip.
3. USB Connector.
3. All You Have and you a ready to Go.
4. Open Odin
5. Tab to Download Mode (( Start + Down Vol ))
6. Connect USB
7. Make Sure the port com detected.
8. Put the Pit file to PIT. Make Sure the PIT is GT-P6800 PIT for P6800XXLQ1_P6800OXALQ1_ATO.pit
9. On Files PDA Make Sure it's XXLQ1_OXALQ1_ATO.md5
10. Make Sure Tick Re-Partition, Auto Reboot and F. Reset Time
11. If you are Ready. Hit the START.
12. If you are successful Com Port box on the Blue and Green in color after the reset and show a pass.
(/snip)
I am confused ... should i tick it or untick it? ... it seems to automatically tick itself on whenever you add a .pit file - so far i UNticked the repartition option
I guess I need to go the whole "adb" route, but it seems to be way over my head ... I cant even get adb to run (a dos window opens and closes immediately) ... pretty frustrating ... there are 70 pages or so to read ... and while I do understand the whole concept, I cannot do it (operationally) ...
well, insult coming to injury ... I am also looking for a job and need my cel desperately
again, thx to all the folks looking into the matter and lending a hand!
cheers, Al
Click to expand...
Click to collapse
Dude dd you get through? If not just go to here: http://www.sammobile.com/firmware/?page=3&model=GT-P6800&pcode=0&os=1&type=3#firmware
and download the latest file.
1. It will download as a zip file so make a new folder on your pc and extract it there.
2. Start odin and dont tick anything! leave everything as is. then select pda and choose the extracted file and press start.
3. after you do that just look fror rooting instructions.
BEWARE! DONT WIPE WITH OFFICIAL RECOVERY BECAUSE YOU'LL LOSE EVERYTHING!
dude, thats exactly what I am doing - and it works (all img transfer correctly, i get "PASS" in odin) ... but the tab still is hanging in a boot trap.
I seem to have those dreaded corrupt blocks in the internal SD ...
UPDATE!!!!
UPDATE!!!!
UPDATE!!!! - finally some light at the end of the tunnel ...
I seem to have managed to push HC 3.2 (Hong Kong version, which is where my tab came from) somewhat successfull on to the tablet... but I still get the following error messages
after a reboot, I get to the following screen:
COULD ANYBODY PLS TRANSLATE THIS !!!!!!!... and better yet, suggest what to enter ... I am stuck right there, no idea how to move on (enter doesnt do the trick, nor my google account name ...)
the good news is, other than that the tab behaves pretty normal (volume rockers really increase/decrease volume, keyboard works normal, i can get into a (chinese) shut down menu and it shuts down pretty normally (as opposed to a hard reboot)
would a hongkong 3.2 pit file help with mounting the e: drive?
any thoughts
thx, Al
Enter your password
Sorry, please retry!
word by word translation as you requested.
Sent from my GT-P6800 using xda app-developers app
bruce16878 said:
Enter your password
Sorry, please retry!
word by word translation as you requested.
Sent from my GT-P6800 using xda app-developers app
Click to expand...
Click to collapse
the /data partition is corrupted... you need to repair it for the device to be fully functional.
edan1979 said:
the /data partition is corrupted... you need to repair it for the device to be fully functional.
Click to expand...
Click to collapse
any pointers on HOW ¿¿¿¿
thx, Al
read this guide carefully http://forum.xda-developers.com/showthread.php?t=1862294
ONLY FOLLOW PART 3 to check your /data partition... starting from this point
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
edan1979 said:
read this guide carefully http://forum.xda-developers.com/showthread.php?t=1862294
ONLY FOLLOW PART 3 to check your /data partition... starting from this point
Code:
Now we are going to use e2fsck to check our new partitions for errors, but not only, it also fixes some erros and it will even for example create lost & found in /data
Click to expand...
Click to collapse
Hi there,
there def. is a problem in the /data directory ... it cannot be mounted and it cannot be formated out of cwm v5.0.2.7
below i have a snip of what I did with e2fsck ... there seem to be some problem
_____________________________
C:\Program Files\Android\android-sdk\platform-tools>adb devices
List of devices attached
46411980122B42BE recovery
C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # e2fsck -yfDC0 /dev/block/mmcblk0p10
e2fsck -yfDC0 /dev/block/mmcblk0p10
e2fsck 1.41.6 (30-May-2009)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
10
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # e
C:\Program Files\Android\android-sdk\platform-tools>
_____________________
what is my problem with e2fsck¿
thx,
al
Step by step you will get there.
Regards,
Axelman
Axelman8 said:
Step by step you will get there.
Regards,
Axelman
Click to expand...
Click to collapse
Just to close this chapter ... and for reference to other future folks ...
I managed to get my tab working again, but it was a pita to get there ...:laugh: ... good thing - i learnt a lot in the process
finally i ran a check on the data partition (tool from the superbrick thread) ... and whilst all sectors reported "OK", there was a section where the check took some 10 times longer than normal.
I then used the .pit files provided from the superbrick thread, flashed those with odin, with the option "enable repartition", b/c thats what the .pit files does ... I was quite nervous doing so, though ... I was on the generous side with the "non usable" sectors on the data partition ... so my 7.7 now only has about 8gig of internal SD - I lost about half of it :crying:
then cleared the cache/data/davlic in cmw 6.x ... and flashed the original 3.2 rom over, which booted up - then flashed the shangha ( or so ?) Rom from the developer section a slim version of ICS 4.0.4.... and voilá ... the tab runs like a champ!
cheers,
al
First of all,
Sometimes we facing BOOTLOOP, but we rarely make a backup so DATA in that backup already out to date.
And i found a method which can FIX BOOTLOOP WITHOUT RESTORING OLD BACKUP !
CAUTION !
THIS METHOD ONLY FOR ANYONE WHO FACING BOOTLOOP AFTER INSTALLING APPS, MODS, ETC
AND THAT APP IS NOT IMPORTANT FOR YOUR ROM
Things you will need
PC or Laptop
USB Cable (For connecting SD-CARD)
SD-CARD Reader (If your CWM Recovery can't mount SD-CARD)
WinRAR or WinZip
Notepad++
Patience!
Click to expand...
Click to collapse
So, lets begin..
STEP 1
If you facing bootloop after installing apps, mods, etc.
YOU MUST REMEMBER THE NAME AND LOCATION OF APPS/MODS YOU'VE PREVIOUSLY INSTALLED
Click to expand...
Click to collapse
STEP 2
Download my CWM zip HERE
Click to expand...
Click to collapse
STEP 3
In PC, after download, extract zip, open META-INF > com > google > android
Open updater-script with Notepad++
Click to expand...
Click to collapse
STEP 4
Edit this line
Code:
delete("/system/app/Home.apk","/system/etc/permissions/com.sonyericsson.uxpres.xml");
with name and location of apps/mods you've previously installed
Ex.
Code:
[CENTER]delete("/system/app/Crap.apk");[/CENTER]
And if you installed more than 1 app, you can insert another name and location in 1 line
Ex.
Code:
delete("/system/app/Crap.apk","/system/etc/permissions/com.bluesky.nxp-resolution.xml");
Click to expand...
Click to collapse
STEP 5
Save your modified updater-script and zipped the META-INF and system folder
Click to expand...
Click to collapse
STEP 6
Put your modified zip to your SD-CARD with mount sdcard option in CWM (with USB Cable) or using SD-CARD Reader
Click to expand...
Click to collapse
STEP 7
Flash It !
DONE !
Click to expand...
Click to collapse
Thanks, its is a lot easier to do with adb file manager thingy software I found online, connecting to pc via usb gives full access to phone file system partitions with root access, just deleting the files with it also works. :thumbup:
Why are SMARTphones soo... Freaking Dumb?
Or via adb
Connect phone/tablet to pc
In adb type:
adb delete("/system/app/Whatever.apk")
Done...
Disadv: USB Debugging must be enabled...
You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data
Bert98 said:
You sir are awesome, I flashed a zip that caused my Xperia U to bootloop and I couldn't delete the file I flahed via ADB! This is a simple yet amazing script, thanks for avoiding me to wipe data
Click to expand...
Click to collapse
You're welcome
Before I tried the tutorial you or even try out all of the tutorials available on the internet, please help me to conclude my problem.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
hey the link isn't working anymore? can you please reupload?
Do you have to get into recovery? as i have no recovery on my phone Xperia z3
I was frustrated by the huawei encryption and decided to get rid of it once and for all.
At first I faced many bootloops but i finally figured out what was going on. Formatting user data through TWRP is not enough because after booting the device, encryption is still there. This happens because the kernel encrypts the device when booting up. Simply modifying the boot.img file to remove file encryption also doesn't work because you still boot into an already encrypted stock user data. So the answer was pretty obvious by now.
The trick is to format data using TWRP AND THEN boot to bootloader to flash a modified boot without encryption. So let's get to it.
How to create a modified boot.img without file encryption/dm-verity
1. Find and download your current firmware from Huawei Firmware Finder Dtabase (Team MT), or from a source that you trust. (Using a firmware with different cust version or a different update will most likely not work).
2. Download Huawei Update Extractor and use it to extract the stock boot.img file from UPDATE.APP
3. Download ASSAYYED_KITCHEN.
4. Place your stock boot.img file in the "WORK" folder of ASSAYYED_KITCHEN.
5. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 1st one (Unpacking Kernel).
6. The ASSAYYED options don't work for me so i did it manually. Go to your work folder and open the folder boot_unpacked\ramdisk.
7. You will see a file named "fstab.qcom", open it using WordPad.
8. Find the line:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption
and delete ",fileencryption".It should now look like that:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
9. (This step is optional,follow it only if you also want dm-verity removed) Use the same method to remove dm-verity.
Code:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait, verify
(Just delete the ",verify" part.)
10. Save the file.
11. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 2nd one (Packing Kernel).
12. Follow the instructions below to properly flash your modified boot.img and get rid of encryption.
Removing file encryption/dm-verity from the device
1. Unlock your device.
2. Flash this TWRP on AGS-W09 or the appropriate custom recovery for your device.
3. Boot to TWRP and FORMAT user data (note that it is very important to format data and not just wipe it). •WARNING• this will delete all your data!
4. Go back to the reboot menu of TWRP and select reboot booloader (it's important to not allow your device to boot into system yet).
5. Using fastboot, flash your modified boot.img that you created earlier.
6. Reboot your device (you might get a bootloop on the first boot but force rebooting your device again by holding the power button will fix that).
7. After booting up, your device should not be encrypted anymore.
8. You can now use the root method that you like to root your device and internal storage should be visible on TWRP. TWRP backup should also work normally.
How to fix Magisk modules not showing up on Magisk Manager (! /data/adb/magisk_merge.img mount failed error)
I am not going to get into the technical staff you can find more info here
Edit: As of Magisk 19.0, the following method becomes obsolete. Magisk modules should now work as expected without issues. This method now concerns those who want to stick to an older version of Magisk
1. Download f2fsfix-2018.9.2.zip provided by VR25 on the thread above.
2. Download all the magisk modules that you need to flash and place them on your device.
3. Download the latest Magisk uninstaller along with the latest installer.
4. Boot to TWRP and flash Magisk uninstaller. (If you don't have Magisk already installed, skip this step)
5. Wipe Davlik Cache.
6. Install the latest Magisk.
7. Wipe Davlik Cache.
8. Flash the "f2fsfix-2018.9.2.zip" immediately followed by your modules.
9. Reboot (it should take more than usual).
10. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.
Note: This method should also work on similar devices. Just make sure you know how to recover your device in case something goes wrong.
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
TRS_80 said:
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
Click to expand...
Click to collapse
Glad it worked for you. Yes this is the downside. The device already comes with an encrypted userdata, so it needs to be formatted. So anything you do before that becomes obsolete. That's why this procedure is much more convenient when it happens after the unlock,when the userdata is wiped by the stock recovery to get a stock condition.
AGS-L09 LTE
I just followed your detailed guide to my tablet and finished all the processes perfectly.
Working..Twrp, Magisk, removed encryption & verify from boot.img and from Data successfully.
A big THANKS for your guide, links and trick all in one post!!!!.
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
mr_fingy said:
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
Click to expand...
Click to collapse
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device here. If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Thanostsak said:
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device . If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Click to expand...
Click to collapse
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
mr_fingy said:
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
Click to expand...
Click to collapse
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Thanostsak said:
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Click to expand...
Click to collapse
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
mr_fingy said:
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
Click to expand...
Click to collapse
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Thanostsak said:
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Click to expand...
Click to collapse
On it now before work
Extracted stock_boot_(IDremoved).img.gz which contains the img
Will run your guide against this img
---------- Post added at 09:20 AM ---------- Previous post was at 08:33 AM ----------
All done. Nice and easy
No issues other than sweaty palms on Huawei long boot screen after flash :silly:
No reboot loop and no Magisk errors
Much appreciated for the help
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
mr_fingy said:
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
Click to expand...
Click to collapse
Great! If you need anything feel free to ask.
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
TimYuan said:
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
Click to expand...
Click to collapse
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
VR25 said:
Those getting everything broken after a second reboot, try the following workaround...
After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.
Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.
Click to expand...
Click to collapse
Thanostsak said:
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
Click to expand...
Click to collapse
It works!!! You are my hero!
TimYuan said:
It works!!! You are my hero!
Click to expand...
Click to collapse
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Thanostsak said:
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Click to expand...
Click to collapse
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
an-_-dro said:
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
Click to expand...
Click to collapse
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Thanostsak said:
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Click to expand...
Click to collapse
encryption is not a problem. since the first place already done with that data partition.
my problem is system partition, every time i made a change to system (for example deleting chrome.apk), something triggered that makes my system weird (magisk forceclose, all file manager become malfunction because system become read only). something lock my system partition if system change.
i thought change fstab.qcom <mnt_flags and options> ro,errors=panic to >> errors=continue (deleting ro/read only) will change my system behaviour, but it's not
Huawei Partition Kit
This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls all the partitions, so if you are for example under the huawei stock rom, you come back under the huawei stock rom but with more space for the system. It has been tested on a dozen models (PRA, ANE, STF, POT, FIG, AGS, etc.) under EMUI 8, 9 or 9.1.
It supports erofs partitions.
WARNING:
RUN THIS TOOL CLEAR ALL DATA FILES IN YOUR DEVICES. IF POSSIBLE, DO A BACKUP FIRST. USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT.
Installation
1) Unzip the zip file on your PC.
2) In the kit directory, read the readme file in the language of your choice (french, english, russian) and execute the step
Version
Last version is 0.62
Requisites
Custom twrp
10 Go free on your PC
Download
Here
AltairFR said:
Download
Here
Click to expand...
Click to collapse
Hi, you might have linked the wrong file...
I am getting an apk
https://sourceforge.net/projects/altairfr-huawei/files/HWGSIPartitionKit/HWGSIPartitionKit.zip/download
I believe this is what you wanted to post...
Nicknackpaddywack101 said:
Hi, you might have linked the wrong file...
I am getting an apk
https://sourceforge.net/projects/altairfr-huawei/files/HWGSIPartitionKit/HWGSIPartitionKit.zip/download
I believe this is what you wanted to post...
Click to expand...
Click to collapse
https://sourceforge.net/projects/altairfr-huawei/files/HWGSIPartitionKit/HWGSIPartitionKit.zip/download
Thanks, i have set correct link
Thank you dear friend, it really works. I managed to increase the system partition on Huawei Nova 2s on Kirin 960 from 2700mb to 3500mb. In the HWGSIPartition program, I got errors, as I understand it in section B, but in the end everything went well.I wanted to ask you how much you can increase the system partition, in the HWGSIPartition program, there is a figure of 5GB.
Great Dragon said:
Thank you dear friend, it really works. I managed to increase the system partition on Huawei Nova 2s on Kirin 960 from 2700mb to 3500mb. In the HWGSIPartition program, I got errors, as I understand it in section B, but in the end everything went well.I wanted to ask you how much you can increase the system partition, in the HWGSIPartition program, there is a figure of 5GB.
Click to expand...
Click to collapse
Hi great dragon
I have fix errors, in my build of yesterday. To correct on your phone, just flash preavs, preas img in your twrp.
You can also flash with dd tools
The preavs, preas partition are not use in aosp or lineage since android 11. You can also make dload reset to restore huawei stock rom and try last release of my tools
For the size of system, it depend if you use erofs gsi or ext4, or ext4 share block
thank you for an awesome tool. sometimes my stock recovery fails to format but on second attemp it works well. this was a life saving and good relief for huawei device with small system size. now everyone could flash pe a13 etc etc. thank you.
Yes it seems to me that there is a small problem with the formatting, I am testing a version 0.63 which should correct this problem
Hi,
I'm trying to install your LeaOS rom on my P8lite 2017. The phone is unblocked, and I a have already install TWRP. The actually rom is EMUI 8.0.0.410 than I'm trying to reinstall the system partition like you said, before installing your LeaOS.
I saw the Readme.txt where I read than I have to run a script by cmd. I guess it works on Windows system. I'm a Linux user, so I wonder if this script could work on Linux?
RickeF said:
Hi,
I'm trying to install your LeaOS rom on my P8lite 2017. The phone is unblocked, and I a have already install TWRP. The actually rom is EMUI 8.0.0.410 than I'm trying to reinstall the system partition like you said, before installing your LeaOS.
I saw the Readme.txt where I read than I have to run a script by cmd. I guess it works on Windows system. I'm a Linux user, so I wonder if this script could work on Linux?
Click to expand...
Click to collapse
Script is only a dos script, but you can adapt it to bash syntax
Thank for your answer. I'm not familiar with this exercice. I will looking to do that.
Having had terrible experiences in the past resizing the partitions on my Mediapad M5, I am a bit afraid of trying your tool. Has anyone tested it on a Kirin 960s CMR-W09 with android 9/EMUI 9.1.0?
Hello, I've made it to the "5-FlashIMG.cmd" but I can't find that script to execute in the download folder up above. I'm new to this so its most likely I missed something.
I'd appreciate some help!
What files are there in HW and HW-IMG?
*Edit I figured it out. I'm just unexperienced.
Thanks AltairFR for quick reply again. Cheers
!Solved
the script got stuck in middle, asking for yes or no input. after that device is unable to boot or even restore from e-recovery. is there any way to revert the changes done by this script?
abhinavprateek said:
!Solved
the script got stuck in middle, asking for yes or no input. after that device is unable to boot or even restore from e-recovery. is there any way to revert the changes done by this script?
Click to expand...
Click to collapse
You can effectively restore from E-Recovery or with dload method.
But do you have log ?
Original img are in the HW-IMG folder..perhaps just flash it with twrp or fastboot cmd
AltairFR said:
You can effectively restore from E-Recovery or with dload method.
But do you have log ?
Original img are in the HW-IMG folder..perhaps just flash it with twrp or fastboot cmd
Click to expand...
Click to collapse
used dload to flash and revert the changes. for some reason, HW-IMG folder didnt get created
no logs unfortunately, will get it when I try it next time
Hello, can this tool be used on my Honor 6x (BLN)？Because the system of this phone is too small, only 2457MB, I can't flash dotos, thanks!