Root status: Permission Denied
Lets keep this thread reserved only for discussion related to rooting this phone. We haven't achieved root yet but I know the way to do it.
You need to follow this guide in order to root your device: http://whiteboard.ping.se/Android/Rooting
So till now I have been able to:
-Build a new kernel
-Unpacked the kernel using kernel kitchen by championswimmer and flashtool(for the sin file)
-.Made the changes in ramdisk
But the next step requires packing it back again. And for doing that you need the cmdline from the kernel.
Its located in /proc/cmdline.
I tried to view it via adb but obviously the system denied the permission because of no root.
Usually you can easily obtain cmdline parameters from the boot.img itself, but in this case, Sony has done some shizz so that you cant obtain it directly. Plus this is my first Sony device so I dont have much knowledge regarding this..
I wont get much time to work on it becuz of my exams.. that's why this thread is here
If you can help/contribute in any way then you are surely welcome. But no noob posts here.
@InfinityShooter use archi's kitchen for unpacking boot.img
first convert stock kernel.sin file to boot.img(by just renaming it)
archi's kitchen will give you the cmdline and other parameters to pack the kernel..
k2wl said:
@InfinityShooter use archi's kitchen for unpacking boot.img
first convert stock kernel.sin file to boot.img(by just renaming it)
archi's kitchen will give you the cmdline and other parameters to pack the kernel..
Click to expand...
Click to collapse
It doesn't work. Sony uses a different kind of boot.img. I have tried dsixda kitchen also, it didnt work out.
InfinityShooter said:
It doesn't work. Sony uses a different kind of boot.img. I have tried dsixda kitchen also, it didnt work out.
Click to expand...
Click to collapse
oh !!! my old sony xperia m used have kernel .sin which used to convert to boot.img by renaming....
Hmmm... how about using a dd command to extract boot.img to sdcard and then unpack it in archi's kitchen????
k2wl said:
oh !!! my old sony xperia m used have kernel .sin which used to convert to boot.img by renaming....
Hmmm... how about using a dd command to extract boot.img to sdcard and then unpack it in archi's kitchen????
Click to expand...
Click to collapse
I don't know if this can help at all: http://forum.xda-developers.com/showthread.php?t=1659584.
It's been ages since I gave up on linux, even as an amateur, so my knowledge is quite limited and, to be honest, a lot of hunch is involved. That's why I am so hesitant at trying this myself.
Anyway I hope this helps a bit.
Also you can get the latest firmware for D2203 (18.4.C.2.12) from here: https://mega.co.nz/#!bMBg1Rqa!aqGcTv6ved0ifh867pbnVVsc-4t55lR9OOij1iSiNLA, which means that one can probably try without unlocking the bootloader...
I have already made the kernel but needs testing. Anyone here with unlocked bootloader and d2202 can try hotboot this using flash tool.
http://d-h.st/rx7e
Try at your own risk.
There is 0% chance of bricking if you hotboot it.
DO NOT FLASH IT
I've tried the kernel. But I do not know how to enter CWM, whether the kernel already include CWM?
No it is not cwm you have to use adb to mount /system as read/write then push su to /system/bin and you will get root. All you need is get superuser from playstore.
Sent from my D2212 using XDA Free mobile app
Report!
The boot.img which I had posted has been confirmed working.
We now have the correct command for packing the boot.img thanks to @jerpelea
I'll be looking forward to making a recovery from source.
If it works then root is not far away
InfinityShooter said:
The boot.img which I had posted has been confirmed working.
We now have the correct command for packing the boot.img thanks to @jerpelea
I'll be looking forward to making a recovery from source.
If it works then root is not far away
Click to expand...
Click to collapse
will, it work on xperia e3 d2212
android-vinay said:
will, it work on xperia e3 d2212
Click to expand...
Click to collapse
Not now.. only for d2202.
I don't know if this a noob question: in the tutorial InfinityShooter posted earlier it says that the phone must have an unlocked bootloader. Thing is that I am a bit confused in terms of whether the bootloader must be unlocked to obtain the system image or in order to fastboot the insecure image. If it is just to obtain the image then wouldn't it be possible to cook the insecure image using the ROM image that Sony distributed to developers, leading to a solution that doesn't interfere with the bootloader?
after I try the kernel, no bugs are found, everything works fine, like wifi and the other no problem, just given cwm to facilitate root...
CWM
Ok this is the second build of the cwm kernel
You can get it here: https://www.androidfilehost.com/?fid=95832962473396055 Doesnt work
You have to HOTBOOT this kernel
Tell me if it works or not.
Troubleshooting:
If you are stuck at black screen then dont worry. Just press and hold power+vol up keys together for 20 seconds to reboot it.
On rebooting the system will automatically revert to stock kernel which you were using earlier.
Congrats! Your phone is working again!
i must have unlock bl?
Wysyłane z mojego WT19i za pomocą Tapatalk 2
Unfortunately yes. Bad thing is that when we unlock the bootloader the TA partition is formatted leading to various problems with Sony apps.
Okay I need help here. My testers report this kernel as working but it fails to work on my device. Please let me know what happens with you..
Link: http://d-h.st/NFR
Here are the EXACT things I do to flash it:
1. Open flashtool
2. Connect my phone
3. I click on thunder icon in flashtool and choose fastboot mode.
4.I click on "Reboot into fastboot mode[adb]"
5.I click on "Select kernel to hotboot" and open the boot.img inside it.
I look at my phone,its all dark. The blue light goes away
6.I click on check current device status and it shows adb connected
7.Orange led comes up as my phone is connected to pc
I see no sony logo or anything like that.
The screen is still BLACK! One thing I notice is that whenever I press the power key, the screen backlight turns on little bit enough for me to notice the varaiation.
Please post your intruction set if it works out for u.
I can't test it myself since I have locked bootloader but did you try to get a working adb shell at this state? If shell works then you might be able to push su and supersu to the device.
cnagr said:
I can't test it myself since I have locked bootloader but did you try to get a working adb shell at this state? If shell works then you might be able to push su and supersu to the device.
Click to expand...
Click to collapse
Dude I cant see anything on screen and you are talking about pushing files -.-
Dude you said that the phone appears to be connected to the pc in adb state, regardless of the phone screen state. That's where that big if of my suggestion came from.
Related
Hello folks,
just wanted to share with you the subject. I'm not a developer, so I cannot go too deeply in the procedure below. what I can ensure is that is working on my personal device, Padfone 2 model A68, bought in Italy with stock firmware IMM76I.WWE_9.8.8.55-0.
DISCLAIMER
should you decide to go for it, remember, I'm just a simple user willing to share a procedure that worked for him, I'm not a smartphone OEM... Accordingly:
I'll not be held responsible if you brick, melt, destroy your device, by following the below procedure... you are the solely and ultimate responsible of your actions and your property.
if after you unlock or root your phone you need to lock it back, or put it in a Virgin "out-of-the-box" state.... cannot help. consider this procedure irreversible.
If you understand the above and concur, well, you can go for the below procedure. otherwise you're kindly requested to stop reading here and NOT continue. tks a lot.
Backgroung
the rooting method is quite straight-forward, getting a stock boot.img and manipulate its ramdisk so that the device can then boot insecure.
Credits
A HUGE thanks to Schriss for his strong support in letting me understand what I was doin on my device:good:
And also a thanks to ChainFire and his insecure adbd (here)
WHAT YOU NEED
1. a padfone 2 with more than 70% battery available, and the above firmware installed (you might wanna try also if your device has different firmware, but I cannot garantee on the results you'll get.
2. this INSECURE ICS boot.img
OR
2a this insecure JB boot.img
OR
2b. you might wanna try this TW JB boot.img from TW JB
3. a valid ADB and FASTBOOT package (lots available within XDA, or already available if you have andorid SDK installed from http://developer.android.com/sdk/index.html)
4. a valid "su" binary, again you can find it in XDA or attached to this post.
5. Valid usb drivers (see mama ASUS website)
6. the infamous "UnLock.apk" (again kindly provided by ASUS)
ONE CLICK procedure (script based) kindly provided by Padfone.cl
here
OR
STEP BY STEP PROCEDURE (MS WINDOWS OS Only)
0. place all of the files (boot.img, adb and fastboot exe's, SU binary) in one folder of your pc and open a cmd session in it.
1. install drivers at point 5 above
2. Unlock your bootloader: install the apk at point 6. above follows all the instructions to get a bootloader unlocked
3. once done the phone can be put in FASTBOOT mode (black screen with "Fastboot MODE !!!" and ASUS LOGO) , with one of the two methods below.
3a. power off device. then push and hold power on + vol up.
3b. if your device is connected to your pc, verify it is in debug mode (under setup/development) and run "adb reboot-bootloader"
4. if not already done connect the device to your pc and wait the drivers selfconfiguring
5. check if fastboot.exe see your device, type in cmd "fastboot devices", if nothing is shown means you're missing drivers, or using a bad fastboot exe.
6. check if your device boots with the insecure img at point 2. of what-you-need list. type in cmd "fastboot boot boot.img"
6a. if it reboots normally... CONGRATS your device is ok with my boot.img and you can root your phone
6b. if it goes into bootloop or bootlock or in QHUSB_DLOAD state, well sorry you cannot go ahead. just push and hold power on your device. it will reboot using its boot.img Sorry no root for you
7. if you're lucky and you get 6a response, you can now ROOT your device
7a. in cmd session type the below
adb remount (system answer "remount succeded" that's a confirmation you can act as superuser)
adb push su /system/bin/
adb shell
chmod 06755 /system/bin/su
type exit, to get off the adb shell.
7b. Collect superuser.apk at the end of this post and place it in same folders of adb.
In cmd session type
"adb push Superuser.apk /system/app
adb shell chmod 06755 /system/app/Superuser.apk"
IF YOU JUST WANT YOUR DEVICE ROOTED PROCEDURE STOPS HERE FOLLOWING IS JUST an ADDED-ON
8. OPTIONAL just in case you want to keep the insecure adbd onboard, not necessary to mantain root condition.
8a. put the device in FASTBOOT mode as above and type in cmd "fastboot flash boot boot.img", this just overwrite your stock boot.img and inoculate the insecure boot.img in your device on a stable basis.
guess it's all.
let me know if it's working for you gentlemen, and remember the disclaimer above and in general just make sure you always know what you're doin... I'll post the boot.img file shortly during today.
reserved
reserved
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
schriss said:
Hi,
Thanks for a guide, that should make it very easy for Padfone 2 users to get root
Disclaimer mentions going back to Stock and relocking - this would need a separate Guide with disclaimers because it's a little dangerous IF you have flashed anything non-stock into Boot partition and then re-locked. But if rooting was done by fastboot boot, then I believe the device could be re-locked and you would still have your root. Until you flash some Asus official Update which would overwrite /System/bin, making SU disappear.
as for points 8 and 8a, it is possible, that you don't need to permanently flash insecure boot.img. After SU has been pushed to /System/bin, you can try simply rebooting as normal and the file should remain on System partition, which is separate from boot.img. It's quite likely, that root will remain and so no flashing would be needed at all if you want to stay on Stock ROM and just need root
Root is really all about putting SU in /System/bin folder, the rest are tricks to make it happen.
Click to expand...
Click to collapse
yes, I got your points I'm amending the first post. tks
Thumbs up guys. U all did it!
Padfone 2 just got epic! I have been following your thread every single day schriss and ivalex. Well done and heaps of gratitude.
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Scarletdeath said:
After rooting,do you think its possible to flash jellybean using clockworkmod in the near future?Thanks!
Sent from my PadFone 2 using xda app-developers app
Click to expand...
Click to collapse
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Ivalex said:
this kind of stuff require time and testing. and as you said first we need a good CWM porting, than someone to port CM10 or a stock-modified JB when it will be available.
we'll see
Click to expand...
Click to collapse
I think getting CWM should be very straightfoward as soon as someone dumps Recovery partition with the commands posted earlier or in the other thread. Testing it should also be simple because it can be booted like insecure boot :victory:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
kahei036 said:
A very good step for our padfone2!
4.1 is coming very soon (within Dec if Asus didn't lie on us) and unlocking at this stage may void the OTA.. (Given CWM is not avail ATM and it is uncertain how soon can the new rom.zip can be made)
even OTA can be performed, boot img is updated and need to be exploited again (with your experience I think it will be much more straight forward later on tho )
These makes me struggling whether I should unlock my padfone2 now or not..
Anyway, as said this is really a good step to our padfone2 at this stage, keep it up and I am looking forward to some point that I have no more struggle and unleash my beast at once!
Greatly appreciated! :good::good:
Click to expand...
Click to collapse
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
turtle76 said:
Hmmm I keep failing at the last step 7b. Keep getting err msg that installation failed when SuperSU tried to update the binary. On WWE stock now and have tried various SU binaries all with same results....
Any suggestions?
Click to expand...
Click to collapse
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
schriss said:
I'm pretty sure that unlocked Padfone 2 can be relocked with fastboot command just like for example HTC One X. Then it would be possible to use Asus OTA updates.
But I also think Asus OTA could be flashed with CWM. Then, same insecure rooting story starts over.
---------- Post added at 05:20 PM ---------- Previous post was at 05:17 PM ----------
So you installed SuperSU, then rebooted just to be sure and then tried updating?
Anyway, in case of such problems, I think we could push latest SuperSU.apk and other files same way as SU, we just push them to /System/app folder where all apk belong, then reboot.
Click to expand...
Click to collapse
Worked finally Thks for the advice pal
turtle76 said:
Worked finally Thks for the advice pal
Click to expand...
Click to collapse
Thanks for the advice. I'll add also push and chmod commands for supersu as add-on In case of problem as the one You had.
Inviato dal mio PadFone 2 con Tapatalk 2
Great news
The only thing I was waiting for before deciding on buying this device was to see how well its supported by this community. Thanks guys, may be finally time to let my good ol HTC HD2 rest now
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
RagnarokRO said:
Great work Padfone 2 community!
Would like to know if anyone has tried this on the IMM761.TW_9.8.8.55-0 firmware?
Did it work?
Click to expand...
Click to collapse
It shld work. I was trying on tw firmware and didn't encountered issues till step 7b which was due to other issue.
getting mine friday did see on asus site there is a tool for unlock of boot loader.
Is this phone and pad any good? Can not wait for mine
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Burley1 said:
I guess I am stupid because I can't get anything to work.
downloaded everything
but I can't make any commands work
I open the cmd and don't know if the " are suppose to be there or not and nothing works
Click to expand...
Click to collapse
Have you switched to the folder that contains fastboot and those stuffs in command prompt?
Hi, can someone help me with extracting boot ramdisk from boot partition?
I am on Z3 .690 LB and need to modify init.rc and other files. I can without problems extract the boot partition using dd from /dev/block/mmcblk0p14
however the resulting image fails any extraction tries with abootimg or unmkbootimg, reporting that it is not valid Android boot image...
Is it in any way possible to get the ramdisk from boot partition (and best put it modified back)?
Thanks..
I am not an expert in that, but for clarity you need to know that even you decompile and recompile a boot.img and make NO changes you are unable to flash it back on a Locked Bootloader.
gregbradley said:
I am not an expert in that, but for clarity you need to know that even you decompile and recompile a boot.img and make NO changes you are unable to flash it back on a Locked Bootloader.
Click to expand...
Click to collapse
Thanks. At the end I used ability of Xzdr to invoke init scripts...
Sent from my D6603 using XDA Free mobile app
gregbradley said:
I am not an expert in that, but for clarity you need to know that even you decompile and recompile a boot.img and make NO changes you are unable to flash it back on a Locked Bootloader.
Click to expand...
Click to collapse
Hm, just from pure curiosity, I copied boot partition (dd) into file and then wrote it (dd) back unchanged. dd seemed to work, and phone booted normally after reboot. I have locked bootloader....
Did you actually decompile the boot.img? Or just pull it from the rom and push it back?
Its the act of compiling the ROM that needs Sony's keys in order to ensure it boot on a locked bootloader
gregbradley said:
Did you actually decompile the boot.img? Or just pull it from the rom and push it back?
Its the act of compiling the ROM that needs Sony's keys in order to ensure it boot on a locked bootloader
Click to expand...
Click to collapse
Cool, finally I got the answer I was looking for. It is not easy to get the right answers regarding locked bootloaders. It confirms what I was a bit feared, that boot.img is compiled with such keys so without it you can not actually do anything on locked bootloader. And I guess there is no way to get the corresponding key in order to tamper with boot.img in any way. Of course it would lead to people being able to flash what they want on LB.
Ok, so I will have to think and count benefits vs. annoyances if it pays me off to unlock... Thank you.
Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.
That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.
Fingers crossed twrp is possible soon
Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well
Would this method work on CLT-L09 model? Thanks
danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse
fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address
Great, thanks for that! I managed to find it on allrom.ir
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command
otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.
danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
good luck on building lineage, the g6 never had any development so i dont anticipate the g7 will get much either. if i was you id concentrate on twrp so we can at least flash gsi based roms.
Is this the original factory signed rom? (I.e. is it possible to fully flash and relock bootloader?)
Also wondering if anyone has the latest full rom (29.114-16-7).
Thanks in advance!
ptn107 said:
Moto G7 river xt1962-1 firmware 29.114-16-5
firmware_moto-g7_river_xt1962-1_29.114-16-5_copyparts
will be needed for custom roms
firmware_moto-g7_river_xt1962-1_29.114-16-5_full
is all partitions, not required for custom roms, just for curious developers
windows users will need to make their own .bat files I don't use windows
two things:
1. working on twrp for river
2. working on lineageos 16 for river based on payton... errors with some vendor files
actually errors all over
please help I have two newborns and only get a few minutes to myself each night
Click to expand...
Click to collapse
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
smokinu said:
Confirmed that at least boot.img is correctly signed. You rock ptn107!! However I did confirm (from the version number displayed in recovery) that this is 29.114.16 and not 29.114.16-5.
How were you able to extract the partitions? Specifically boot.img. If I can learn that, then it would be easy to unroot, take OTA updates, copy and save boot.img, and patch with Magisk. Thanks in advance!!!
Click to expand...
Click to collapse
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
ptn107,
Thanks for the write-up. I'm familiar with a similar approach using TWRP (booted, but not installed) and dd copying the individual partitions. I will give your script a try. Should save a lot of time!
Is there a way to copy partitions without root? My biggest concern is taking on an OTA update (currently 16-7), without having the original signed images to revert back to stock and relock the bootloader. Motorola has historically been bad at providing factory roms. If there is a clever way to unroot, take an OTA, save original, and re-root....I'd be a happy camper!
/dev is user root and group root so root is necessary.
Is there a clever way to take an OTA update and get a copy of the new boot.img? From what i understand, you have to unroot to take an OTA update.
BTW...good luck with the newborns!! Mine is now 3 and is still as much of a handful as when he was a newborn.
ptn107 said:
The boot image version does not change with every little update. For every version of 29.114.16-* released it will be the same boot.img. 29.114.16-7 is getting around and most likely uses the exact same boot.img as ours.
As for extracting the .img files I use a linux shell script I wrote here. Makes doing this quick with each new firmware image.
It needs to be placed in /sdcard on your device (root is required to work):
Code:
adb push mkimg.sh /sdcard/
adb shell
cd /sdcard/
su -c sh ./mkimg.sh
I do this in Linux. Not much of a Windows user anymore.
Output files go into /sdcard/firmware-images but you can change that with the 'outfolder' variable if you wish.
Long story short it takes the list of partitions from /dev/block/bootdevice/by-name/ and uses 'dd' to create the .img.
If you are looking to just get a boot.img from our device and nothing else the command would be as follows (needs root):
Code:
su dd if=/dev/block/mmcblk0p41 of=/sdcard/boot.img > /dev/null 2>&1
Click to expand...
Click to collapse
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
clcombs262 said:
Boot img sometimes changes, you never know. I bricked a g6 by flashing a boot img that the last number in the version was 2 instead of 4. Flashed, and got stuck in a bootloop. Had to completely reflash stock firmware, then took an OTA that bricked it.
Click to expand...
Click to collapse
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
smokinu said:
I did confirm that the boot.img between 16 and 16-5 is different. The recovery mode displays the correct version for each of the boot.imgs, and MD5 checksums are different, although same file size.
That being said, flashing a 16 boot.img on a 16-5 device will mearly result in bootloop until the correct version is flashed. People should keep track of which slot they loaded the boot.img into (A/B).
Click to expand...
Click to collapse
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
ptn107 said:
Code:
fastboot oem lock
doesn't work with PPO29.114-16-5
says boot.img is not signed
update: same for PPO29.114-16 and PPO29.80-61
Click to expand...
Click to collapse
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
smokinu said:
I saw the same thing on my end at first. Found this to work repeatedly....
fastboot oem lock (enter this a few times until i says something to the effect of...."you still need to flash a signed boot.img")
fastboot flash boot boot.img (this will now flash fine without saying the image is not signed)
fastboot oem lock (if you prefer to re-lock. You'll need the unlock key again if you plan to unlock).
Click to expand...
Click to collapse
Wow. That actually worked. I had to do both commands like 6 times one after the other but it worked.
Thank you!
No problem! Glad I could help. Found that one by accident.
smokinu said:
No problem! Glad I could help. Found that one by accident.
Click to expand...
Click to collapse
I would have never found that out.
fastboot without root
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
The zip file itself cannot be flashed as it's not in proper update format. You'll have to extract and flash the contents via fastboot. To get to fastboot, power off the device then hold power and volume down until you see the bootloader screen, and then connect it via USB to a pc
Follow the instructions here to get back to stock
Mr_navillus said:
I have been foolish and used twrp to wipe my G7. I am trying to use twrp to flash or fastboot update provided in this thread but neither approach works.
error is invalid zip file.
I was running -7 not -5
as in my title, there is no root. and because of my stupidity, no OS either! I am happy to give any details
Any help would be amazing. Thanks in advance!
Click to expand...
Click to collapse
Sounds like you wiped the system partition then tried to flash the unflashable zip file (hence, no system)
First, always make backups.
Second, you can still get into fastboot and manually update/restore
You can also use the moto software to recover the device.
Get it into fastboot, start from there. It is 100% an easy recovery process
warBeard_actual said:
You can also use the moto software to recover the device.
Click to expand...
Click to collapse
This fixed it in a jiffy. Making backups from now on!
Question to the experts:
Unlocking the bootloader and rooting a phone is stressful times for those of us who (like me) only do this once every few years when we buy a new phone. On some phones, after attempts at routing, I've been stuck for days without a phone till some distant helpful person helped me back to a working rooted phone. Other times it was very simple. But the experience leaves you scared.
Yes I know it's my own (and similar other uneducated) fault because we did something wrong that would be obvious to any expert. But it happens to the rest of us no matter how many threads we read.
So my question is, if the phone becomes non functional following erroneous commands or files (my own unintentional error), will this same 'moto recovery' restore things?
Where do I find out more 'how' to use this Moto software and where this 'Moto software recovery' is to be found?
Thank you.
Edit
Just to clarify things, this is my first Moto phone which is why I don't know what the Moto software recovery is. Is it what you get by pressing Power-volume down?
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Gregbmil1 said:
I'm not known for giving good advice but if I was in your situation I would try to install the lastest version of Magisk and hope for the best. Knowing how I am it would be driving me nuts wondering if it would work.
That booster app, have you tried uninstalling it with adb?
Click to expand...
Click to collapse
Hey, thanks for your reply. I am really eager to root it. I almost just went for it. However, then I thought about it. If something went wrong I would not have any way to recover the phone since there is not a system image available yet. I have not given adb removal a try yet as I figure it would just be easier to go with rooting since it will help me with everything I am trying to achieve. If I cannot root it then I will go the adb route. Hopefully someone will come along and help me out. Fingers crossed
Let us know what you end up doing. Are you expected to send the phone back after the beta testing? If you are responsible for any damages done to it, I would not try it.
You could send it back bricked and say you have no idea what happened to it, lol. That or say you were "testing" the security of the device and that it passes
bigroc2223 said:
I signed up for a beta test on centernode and received a smartphone to test. The phone is so new that I cannot find any information about it on the internet. The bootloader is unlocked on it. I was reading that you can use magisk to root any device with an unlocked bootloader and system image. Since the phone is so new I cannot find a system image. Is it still possible to root the device? Is there a way I can backup the stock ROM and create a system image that way? Is there something else that will work? I really want to root the device because it came with a preinstalled app which is a system booster type app. It will not let me uninstall it, disable it, or force stop it. When I install my app for my alarm clock it keeps killing the app and the alarm will not go off. I have went through all of the app settings and cannot get it to stop. It also keeps interfering with my VPN. I would also like to root th device to remove some of the bloatware and to have access to the HOST file. Could someone please help me this? I would greatly appreciate it. Thanks guys!
Click to expand...
Click to collapse
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
dladz said:
If you have the firmware then you're in luck (especially if it's the full one)
Download a program for windows called "Payload Dumper"
Open the zip (firmware) and copy out the payload.bin file.
Copy this to the input folder from payload dumper.
Run the exe for payload dumper
It'll output a bunch of files to output folder
You'll see a boot.img file this is essentially the file you use to boot your phone and also where magisk would reside too.
Copy this to your phone.
Install the latest Magisk then open it
Click install and then patch a file, navigate to the boot.img
Click the boot.img and it'll output a file to "SDcard\Downloads" usually called magisk_patched.img
Copy this to your fastboot folder on your computer and open a CMD / Powershell command to that location.
Then boot to fastboot / bootloader mode
Then type:
fastboot boot "name of patched boot.img"
eg:
fastboot boot magisk_patched.img
The phone will boot
From this point you are rooted but you need to make it permanent as you haven't flashed the boot sector at this point, you're only booting an image, if you were to reboot you'd lose it.
Open Magisk again then click install again.
Now instead of just seeing patch a file you'll see "Install Directly" + "Install after an OTA"
Click Install directly, allow it to finish, then reboot.
You're now fully rooted.
Heres my guides for the oneplus 8 pro, don't use the images there as they're for the 8 pro, you also can download payload dumper from there too.
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com
IT's easy.
Good luck
Click to expand...
Click to collapse
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
bigroc2223 said:
So it sounds like since this is a beta device and I cannot find a firmware image in out of luck?
I guess the only other option I have is finding someone who can port twrp for my device. Then I can just root via TWRP. However, from what I have read that might not even be an option as Android 11 mostly has to be rooted the hard way which you have gave instructions on above.
Can anyone think of anything else I can try?
Click to expand...
Click to collapse
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
dladz said:
You can also extract the boot image... Can't remember the commands for this via ADB, Google ADB extract boot.img
Click to expand...
Click to collapse
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
bigroc2223 said:
Awesome this is exactly what I was trying to figure out in my original post. Since there is no stock firmware available yet (beta unit) what is the best way to backup the device so I do not get a brick in the process? Thanks again for your help.
Click to expand...
Click to collapse
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
dladz said:
An actual back up? Probably twrp if available.
If not then you'd need a recovery method.
So providing you have a recovery solution you should be fine.
Click to expand...
Click to collapse
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
bigroc2223 said:
Ahhh okay since it is a beta device no one has made TWRP for it yet. What do you think the risk is of manually pulling the boot img, patching, and flashing is? If I can get that to work I will try to port twrp to the device. Thanks again for the help.
Click to expand...
Click to collapse
You're very welcome.
Chances of it not booting after doing that? Absolutely zero.
It's a copy not a cut, so you're fine.
The only problem you may encounter is the ability to access the device on that level.
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
I would advise against flashing it, just boot it.
dladz said:
Just turn on usb debugging and make sure ADB works as it should be checking on ADB devices.
Then go ahead with the pull.
You'll be fine.
Also once you have the boot.img if the patched one doesn't work then just reboot and you're back to normal.
Click to expand...
Click to collapse
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
jwoegerbauer said:
You can't simply run
Code:
adb devices
adb pull boot.img > C:\boot.img
to clone phone's boot.img to PC.
The correct way is described here
Extract Boot.img Directly from Device Without Downloading Firmware
In this tutorial, we will show you the steps to extract the boot.img file directly from your device without downloading the firmware.
www.droidwin.com
Click to expand...
Click to collapse
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
bigroc2223 said:
Thanks for your help guys I appreciate it greatly. I am going to give this a try today. I will report back and let you guys know how it goes.
One last question. Since this beta unit I got is a tracfone branded unit with an unlocked bootloader is it possible that they could push a firmware which will lock the bootloader at some point? If so is there any way to prevent that from happening? Thanks again for all your help.
Click to expand...
Click to collapse
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It's a phone for testing which I am allowed to keep.
dladz said:
Possible yes, but I doubt they would do that.
Is it an ambassador phone? Or for testing?
Locking the bootloader wipes the phone so I wouldn't imagine they'd do that without forewarning.
Plus locking a bootloader comes with its risks too, so you could say that it broke from the update.
But it won't come to that, I've had several ambassador phones myself and honestly they're fire and forget for the most part, I wouldn't worry about it
Click to expand...
Click to collapse
It is a phone for testing which I am allowed to keep. Specs are Snapdragon 750g, Adreno 619, and 4gb of ram. Not too shabby for a free phone. It is a lot snappier than the moto e6 I was previously using.
dladz said:
I did not say that you could?? I said pull it.
Before that I said look it up / Google it
Click to expand...
Click to collapse
This method requires TWRP. So this will not work.
bigroc2223 said:
Nvm
Click to expand...
Click to collapse
dladz said:
Again!!!? What's your problem??
You're just trying to (for whatever reason) prove me wrong and yet again I wasn't being descriptive of an ADB pull!!!
You're pulling the boot.img off the device by whatever means.
To be clear for the final time, I'm not stating to use twrp, a script or anything else I said look it up / Google it!
Now if you've helped the chap then that's great, looking at what I said and attempting to put me straight when you clearly don't have to, is no help to you or the chap needing help it's just making you look like you're on a power trip.
Click to expand...
Click to collapse
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
bigroc2223 said:
I'm just trying to get some help here guys that's it. I appreciate everyone's efforts and opinions. Let's all try to work together and try to find a solution peacefully please.
So far I have adb installed and working. I have tried to use the commands I was able to locate via google. So far nothing works. I have also tried uninstalling some programs using adb which did not work. I think I am going to have to find someone who could port twrp for me
Click to expand...
Click to collapse
Sorry I got the wrong end of the stick, I thought you was a second person posting..
Forget what I said