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,
I tried finding a better place to post this, but there are no device forums for the bSquare MDP 8660 probably because its not that common and its a 'development phone'.
I'm using one of these devices in the lab I'm working in and I wanted to see if I could flash Google Apps on it since it comes without any of them (Market, Maps, Gmail, etc.).
Since it has an unlocked bootloader, can I just flash Google Apps (from Cyanogen's website) to it the same way you do it when installing the Cyanogen ROM? Are these files device independent? Or would this be an almost sure way of bricking the phone?
Device website: bsquare.com/snapdragon-mobile-development-platform.aspx
OS: Android 2.3.4
I would really appreciate any guidance/suggestions. Thanks!
gjain89 said:
Hi,
I tried finding a better place to post this, but there are no device forums for the bSquare MDP 8660 probably because its not that common and its a 'development phone'.
I'm using one of these devices in the lab I'm working in and I wanted to see if I could flash Google Apps on it since it comes without any of them (Market, Maps, Gmail, etc.).
Since it has an unlocked bootloader, can I just flash Google Apps (from Cyanogen's website) to it the same way you do it when installing the Cyanogen ROM? Are these files device independent? Or would this be an almost sure way of bricking the phone?
Device website: bsquare.com/snapdragon-mobile-development-platform.aspx
OS: Android 2.3.4
I would really appreciate any guidance/suggestions. Thanks!
Click to expand...
Click to collapse
Most probably yes.
Well here's my advice. Follow at your own risk. It might not probably brick it but there's always the slight risk of stuff going awry.
1) Make a Flash backup.
2) See if you have the system/app folder intact.
3) Flash the Google Market(yes, only the market.)
4) Install whatever the apps you want from the Market.
All Google apps except Market and Talk can be downloaded from the Market. You can of course flash the whole gapps update but downloading this way gives you some peace of mind and chances of avoiding any possible incompatible apps. (Like Voice Search which may not work properly on all ROMs. But, if it's AOSP, all Google apps would work and should work. )
Most of the Google apps would be device independent since most of them would use the Android API and not the native platform.
Flashing custom recovery - didn't work
Thanks for the guidelines.
I tried flashing ClockworkMod recovery so that I could make a backup of the phone, but every time I boot into recovery it shows a blank screen now. ADB doesn't recognize the device either. I tried Amon Ra's recovery and the phone is doing the same thing.
Before flashing any of the custom recoveries, the phone would just show the triangle when booting into recovery. It did show up on ADB though.
Would you have any suggestions on how I should continue? In case its of any use, I do have a package that I downloaded from the manufacturer's website that contains the original boot, recovery, and system images (along with some other files).
gjain89 said:
Thanks for the guidelines.
I tried flashing ClockworkMod recovery so that I could make a backup of the phone, but every time I boot into recovery it shows a blank screen now. ADB doesn't recognize the device either. I tried Amon Ra's recovery and the phone is doing the same thing.
Before flashing any of the custom recoveries, the phone would just show the triangle when booting into recovery. It did show up on ADB though.
Would you have any suggestions on how I should continue? In case its of any use, I do have a package that I downloaded from the manufacturer's website that contains the original boot, recovery, and system images (along with some other files).
Click to expand...
Click to collapse
As I told earlier, I'm not so familiar with the device.
If ADB is not working in recovery, it could either mean that the USB drivers(the drivers in the device, not PC) are corrupted or that the recovery is incompatible.
If CWM recovery you used is 100% compatible with your device(ie other people are using it without issues), it means that you must reflash all your files to factory and then flash a fresh copy of recovery. Simply, you must start it from scratch.
If you have no idea of the compatibility of CWM with your device,
1) Check and see if ADB/fastboot is working well with your device in other modes(boot, system). You can perform a simple file transfer and check the checksum of the original copy and copy on your device to ensure integrity.
2) If ADB/fastboot works well in all other modes but fails only in recovery, flash stock recovery(only recovery) and see if adb is working well. You can do the same thing as before. If adb/fastboot works well in stock recovery but fails in CWM recovery, it probably means CWM is not fully compatible with your device.
If CWM works well, go ahead and make a backup and proceed to flashing market. But, if like I said in 2), if CWM is not fully compatible with your device, proceed with caution.
As an an alternative, if you are going through all these ONLY to get the market, you can extract the market update and push the relevant files to the correct paths in the device using ADB in recovery or bootloader mode.
Installing only the Market app
Hi Nibras,
Sorry for not replying back to you. My college classes got started and I couldn't spend much time on this project.
I liked the idea of just extracting the Market app and installing that (since that is all I really need).
Do you think I could just use the procedure outlined below, even though I won't be doing it on Honeycomb:
Installing Android Market over your freshly installed HoneyComb will require a different approach than just installing an APK.
Make sure you have ADB up and running, and your device recognized. Refer to our guides on what is ADB and how to install it, and how to enable ADB USB drivers for NVIDIA Tegra and Tegra 2 based devices.
Download this version of the Market (2.2.11).
Download GoogleServicesFramework.apk.
Place the files in any folder on your computer and open a Command Prompt window, browsing to that folder.
Enter these commands in the Command Prompt window:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb push Vending.apk system/app/Vending.apk
adb push GoogleServicesFramework.apk system/app/GoogleServicesFramework.apk
adb shell
cd system/app
chmod 6755 Vending.apk
chmod 6755 GoogleServicesFramework.apk
exit
adb reboot
Now go to apps, open the market and sign in. If the Market won’t open at first, reboot and try again and it should work.
Click to expand...
Click to collapse
gjain89 said:
Hi Nibras,
Sorry for not replying back to you. My college classes got started and I couldn't spend much time on this project.
I liked the idea of just extracting the Market app and installing that (since that is all I really need).
Do you think I could just use the procedure outlined below, even though I won't be doing it on Honeycomb:
Click to expand...
Click to collapse
That should work I guess. But, flashing via recovery is just a one step process. =)
Update.zip also does just the above process, I guess. It just saves us a couple of steps. Also, if you make a recovery backup, if anything goes wrong(say boot loop or force close of system at boot), you can revert very easily since recovery is independent of all the other data on phone.
And, I guess you might have to push Talk.apk too. I'm not sure about it though. Some people complained that removing Talk.apk broke the Market authentication.
If you want to push Talk.apk, get the apk file and,
Type adb push Talk.apk system/app/Talk.apk after adb push GoogleServicesFramework.apk system/app/GoogleServicesFramework.apk
Also, type, chmod 6755 Talk.apk after chmod 6755 GoogleServicesFramework.apk.
Btw, you can also ignore Android Market altogether and use Amazon App Store as well as GetJar.com. They both offer install-able Market apps. Of course, they don't have a collection as large as Android Market.
@gjain89:
Did you ever try pushing the Market files to the MDP? If so, then did it work? I have one of these and I'm in a similar position.
Thanks
I have one of these...
I used adb to push the files. However the system partition barely has any room for more apps. so apps larger than 2MB won't install, unless you obtain the APK from a secondary source.
Refer to this thread for more information: http://forum.xda-developers.com/showthread.php?t=1400737
And this one: https://developer.qualcomm.com/forum/qdevnet-forums/general-discussion/6864
Plus, many apps force close.
Enjoy!
PS: Let's try to stick together, we might be able to fix some of these problems. Maybe someone could build a custom rom.
Hello,
as many may have noticed with the new stock ICS ROM there are some issues regarding links, e.g. WhatsApp crashes if you click on a link etc. and there is a quick fix/workaround for it (you need write access to /system however).
Investigating the crash report it became clear that the issue is related to the Htc Linkify Dispatcher which was (as I understand it) implemented by HTC to comply with some apple patent-related stuff and to strip the device of Android's original abilities regarding the handling of links (more info e.g. on [1] )
So normally the device will have a running Htclinkifydispatcher.apk and in addition a build.prop setting indicating this "feature". With the ICS ROM however the build.prop says that the feature is enabled but a quick check in /system shows that the Htclinkifydispatcher.apk is not installed, so consequently this means that apps relying on build.prop will fail when handling links (as the dispatcher is not active).
The logical solution seems to be to adapt the build.prop accordingly. After a quick search I found the necessary steps to be the following (Source: [2]):
In the /system/build.prop file search for ro.da1.enable=true and set it to ro.da1.enable=false
Add ro.da1.method=false directly under it
Reboot
I performed these steps and now am able to click on links in WhatsApp again without crashes. Maybe this will help someone else as well.
Cheers
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
[2] androidcentral.com / how-restore-functionality-apple-v-htc-war-has-taken-away-root
Sorry for the awkwardly typed web URLs but I do not yet have the privilege to post outside links, so maybe some mod can fix it
some moderator should make this sticky.
yes this is the exact problem i encountered, in every apps except internet.. -.-
thanks!
nice guide everything ok now! :victory:
Thanks for this workaround. However I noticed that I no longer have an option called something like "Aplications associations" under Settings menu. It was just below "Applications"... Do you think is related to the modification?
I think yes...
From what I have understood reading
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
the Apple patent is that when you click on a link (or something recognised usefull data...) a popup menu appear letting you choose what to do.
HTC removes that ability and using Htclinkifydispatcher.apk with "Application Association" gives you the choice (but only one...) of what to do on a specific type of link.
Since the workaround we are talking here needs rootted phones, could be also another solution to put in /system/app the Htclinkifydispatcher.apk and leaves build.prop as it is (to stop crash on link) ?
fblasot said:
I think yes...
From what I have understood reading
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
the Apple patent is that when you click on a link (or something recognised usefull data...) a popup menu appear letting you choose what to do.
HTC removes that ability and using Htclinkifydispatcher.apk with "Application Association" gives you the choice (but only one...) of what to do on a specific type of link.
Since the workaround we are talking here needs rootted phones, could be also another solution to put in /system/app the Htclinkifydispatcher.apk and leaves build.prop as it is (to stop crash on link) ?
Click to expand...
Click to collapse
thanks for this, it works
where can we get the correct htclinkifydisptcher.apk that will work on the stock desire s ics rom?
can you post a link please
I don't have a link but you could try to extract the apk from any HTC ICS sense 4 original rom.
Anyway, I read in an other discussion that also with this apk there are some limits and then the mod of build.prop it is the better solution.
Who's awesome? You are
Worked for me! Thanks dude!
hahnbanach said:
Hello,
as many may have noticed with the new stock ICS ROM there are some issues regarding links, e.g. WhatsApp crashes if you click on a link etc. and there is a quick fix/workaround for it (you need write access to /system however).
Investigating the crash report it became clear that the issue is related to the Htc Linkify Dispatcher which was (as I understand it) implemented by HTC to comply with some apple patent-related stuff and to strip the device of Android's original abilities regarding the handling of links (more info e.g. on [1] )
So normally the device will have a running Htclinkifydispatcher.apk and in addition a build.prop setting indicating this "feature". With the ICS ROM however the build.prop says that the feature is enabled but a quick check in /system shows that the Htclinkifydispatcher.apk is not installed, so consequently this means that apps relying on build.prop will fail when handling links (as the dispatcher is not active).
The logical solution seems to be to adapt the build.prop accordingly. After a quick search I found the necessary steps to be the following (Source: [2]):
In the /system/build.prop file search for ro.da1.enable=true and set it to ro.da1.enable=false
Add ro.da1.method=false directly under it
Reboot
I performed these steps and now am able to click on links in WhatsApp again without crashes. Maybe this will help someone else as well.
Cheers
[1] commonsware.com / blog / 2012 / 07 / 23 / linkify-problem-patent-behavior . html
[2] androidcentral.com / how-restore-functionality-apple-v-htc-war-has-taken-away-root
Sorry for the awkwardly typed web URLs but I do not yet have the privilege to post outside links, so maybe some mod can fix it
Click to expand...
Click to collapse
I specifically rooted and unlocked my phone to do this as it was annoying as hell!
Thanks! :good:
You have unlocked the bootloader via HTC? If yes, after that what Guide for rooting have you used? I'm in the same situation as you are, I'm doing this only for the links. Stupid Apple patent! Also, if I un-root / re-lock the bootloader, the change remains? If I re-lock, would it show "Locked" or "Re-locked"?
Yes, unlocked via HTC-Dev. Can't remember the guide I used as I looked at a few for it to make sense to me.
In short, Unlocked boot loader, flashed ClockWorkMod recovery, then flashed super user. - You will have to find the guide that works best for you.
I have left it unlocked, but if you do re-lock it will say - Re-Locked, SECURITY WARNING. Nothing to worry about, just that HTC will know you have unlocked your device if you ever send it in for repair, not a problem for me as my phone is over a year old now.
I did notice though that if you DO re-lock the bootloader and try to edit the Build-Prop, it will always revert back to what it was before.
I had to leave it unlocked to edit it, and I haven't re-locked it.
MalekoUK said:
In short, Unlocked boot loader, flashed ClockWorkMod recovery, then flashed super user. - You will have to find the guide that works best for you.
.
Click to expand...
Click to collapse
... this is my big problem! 4ext / clockworkmod / superoneclick ... mount SDcard... don't mount SDcard... install HTCsync, uninstall HTCSync... Help?
Spiry0r said:
... this is my big problem! 4ext / clockworkmod / superoneclick ... mount SDcard... don't mount SDcard... install HTCsync, uninstall HTCSync... Help?
Click to expand...
Click to collapse
All I did was put superuser on the SD card, then installed the superuser zip via clockworkmod recovery, worked a charm. Anything else you will have to search the forum as I just jumped through a few threads to get the best method for me.
All the answers are in the forums
Thanks man.
For them, who doesn't know what is this all about.
After this fix>
o-> links in facebook work again - automatically open webrowser by clicking on link
o-> you can click on number in SMS message and this number automatically get transfered to dialer, so you can call it, or store to your contacts
o-> moar and moar, i have tried these two, because it was quite serious bug for me
thank you. Htc evo 3d with coolsense rom here had same problem that fixed it
Thx! this solved my problem!
this should be stickied or put in the INDEX thread.. thanks a lot for this, OP!
Spiry0r said:
... this is my big problem! 4ext / clockworkmod / superoneclick ... mount SDcard... don't mount SDcard... install HTCsync, uninstall HTCSync... Help?
Click to expand...
Click to collapse
before you do anything, back up everything that can be backed up, such as contact, smses, APN settings and apps if possible.
after that, change the sd card with a blank one (this isn't necessary, but just to ensure that you will not erase your current sd card and the files inside it)
1. unlock the bootloader (follow the steps closely and also install all necessary files as mentioned in the instructions)
2. download necessary custom recovery (4EXT is what i recommend) and SU zip files, put in the root of the blank SD card (that is, not inside any folder, for the sake of convenience)
3. boot into recovery (can be done in several ways, easiest one is power+vol down and get to recovery from bootloader screen, but remember to turn off fastboot in settings)
4. flash the custom recovery first. Once finished, my suggestion is turn off the phone
5. boot into recovery again, it should now be the custom one
6. flash the SU zip..
7. done, you are now rooted with stock ROM
experts please feel free to add on or correct any mistakes..
sorry if I got off track a little, just want to offer some help because I'm in a good mood today..
hahnbanach said:
(you need write access to /system however).
Click to expand...
Click to collapse
I tried frm es note editor in es file explorer but got error saving the file how do I get write access to /system ?
urmish101 said:
I tried frm es note editor in es file explorer but got error saving the file how do I get write access to /system ?
Click to expand...
Click to collapse
In es file Explorer options. And remember you'll need to enable "browse as root" or something similar as well.
Google Store purchased, currently have root and twrp installed, bootloader unlocked.
I read briefly that to accept the new update and keep root, you have to mess with the bootloader? Is there some sort of simplified guide on this?
Thanks to chainfire, there is a guide for updating to may version and keep may bootloader.
First, you have to flash new factory image or sideload the ota
Let it reboot, now you lost recovery, custom kernel, root etc..
Reboot to bootloader and boot to twrp, flash supersu and the zip provided by chainfire for signing the bootloader
Reboot and you should have root with may update
If you want a custom kernel or twrp you should flash the zips and the verification tool, i didn't understand the right process for this, for me it looped a couple of times but after flashing those files a bunch of times in different orders it succesfully booted with no errors.
I'm currently running stock 7.1.2 may update with supersu 2.79 SR3, TWRP 3.0.1 RC1, franco kernel r15 with no errors, everything running perfectly
Where can we get the May ota download and a refresher on sideloading it? I've done that before but don't do it often enough to get through it quickly... currently running 7.1.2 / NHG47K on my Google bought Pixel which has been unlocked, and rooted. Though I've not installed TWRP, I can bootload into it fine....
My phone app has suddenly started acting all wonky, so I'd really like to update and see if that will help straighten things up.
Thanks for the assistance...
Got the May ota and will now sideload it. Where is this 'guide' that you mentioned Chainfire has setup to assist folks handling the May update?? I'd like, specifically, to get a copy of the zip file that signs the bootloader.
Thanks!!
I am wondering also. Still using NDE63P from October, wasn't aware we could take OTA's at all and keep root. Been having so many Bluetooth issues, it's worth a shot given their focus on it a month or so ago.
Well... up until this recent May ota release, it used to be pretty easy to simply download the latest Superuser zip file and re-install it on your phone, thereby re-establishing root access (assuming your phone is / was unlocked and rooted prior to taking the update). That is not the case going forward.... but I am still researching it.... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Oh wow, that's super easy. Sweet! Now I need to find out where the past OTA's are so I can flash all of those...
I'm going to give all that a try soon, if anyone following this thread needs help or has questions, feel free to reply here with them.
To dumb down that entire OP into the reason why it's needed: the OTA's being sent out up through April 2017 was just the OTA itself. In May, they started requiring them to be encrypted with a certificate, but didn't provide requirements on from whom the certificate comes from. This means that now, instead of just flashing the ZIP, you first encrypt it with your own certificate and then flash the result of that.
They mention the private keys can be discarded later, given they are generated for the sole purpose of uploading OTA's to the phone, I would think keeping them on the internal SD card of the phone itself would be suitable. Heck, zip those puppies up and email them to yourself, they're not being used for security, why not, right?
Try here: https://developers.google.com/android/ota
Just sideload the latest... you only need one
pstgh said:
... https://developers.google.com/android/ota
Just sideload the latest
Click to expand...
Click to collapse
pstgh said:
... follow along by looking here: https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
Click to expand...
Click to collapse
Yes, the first link is the ota repositories, download the zip of may, then put it in the adb folder, reboot to recovery, go in advanced menu and start sideload, without wipe cache or dalvik.
Then in cmd just type "adb sideload <name-of-the-ota.zip>"
Let it finish both steps and reboot, then you are ready to boot to twrp and flash supersu and the zip v3 from chainfire's thread for signin the bootloader.
That's it
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
pstgh said:
Agree. Pro tip: after downloading the proper ota update, rename it to something simpler so you can more easily enter that adb sideload ota-filename.zip command!
Click to expand...
Click to collapse
better pro tip: tab auto completes the filename.
exad said:
better pro tip: tab auto completes the filename.
Click to expand...
Click to collapse
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal.
(I use ConEmu, so right-clicking the terminal itself pastes what's on the clipboard; some Linux distros do this also Command Prompt I think right click is done on the title bar or some obscure thing like that, can't remember).
Expert pro tip: shift+right click the file, "Copy As Path", paste into the terminal. -
I like this one but when I tried it, fyi, it pastes the path with quote marks on either end.... which is burdensome
Quotes are accepted in the adb commands. Without them, each space in the path is interpreted as an argument delimiter.
adb some-command C:\Program Files\Some-Program\Main.exe
passes "C:\Program" and "Files\Some-Program\Main.exe" as two different arguments to adb. Surrounding it with quotes instead allows adb to use the full path correctly. Common practice with command-line apps, although not universally supported.
It does work with adb/fastboot though, just did it a couple days ago to upgrade my Huawei Watch with the Wear 2.0 OTA that it kept failing to detect was available.
Despite it sales wise, one of BLU (Bold Like Us)'s best selling phone, for some reason their G90 Pro model has very little information as far as specific rooting tutorials.
Anyway, straight forward goal, I think. Since again, no information and I'm not sure if that is because of no one asking questions or if it is actually extremely difficult or not.
I'm trying to root by BLU G90 Pro so I can use an app from the Google Playstore called "Battery Charge Limit [ROOT]" by someone called "SL/\SH". That's about it.
This is also the first time I ever done something like this so feel free to go super in depth if necessary as I'll probably need the step by step. No matter how small the step is, imo it would probably be a good idea to mention it anyway since I will probably not know.
PS: Everything is backed up in case something goes wrong so I'm ready to experiment as needed.
This isn't a time sensitive goal either so by all means take your time during this discussion.
just use rootallmtk by diplomatic .. i can help you but you provably need to deal with Android 10 partition being read-only PM me if you're interested
Spearra said:
Despite it sales wise, one of BLU (Bold Like Us)'s best selling phone, for some reason their G90 Pro model has very little information as far as specific rooting tutorials.
Anyway, straight forward goal, I think. Since again, no information and I'm not sure if that is because of no one asking questions or if it is actually extremely difficult or not.
I'm trying to root by BLU G90 Pro so I can use an app from the Google Playstore called "Battery Charge Limit [ROOT]" by someone called "SL/\SH". That's about it.
This is also the first time I ever done something like this so feel free to go super in depth if necessary as I'll probably need the step by step. No matter how small the step is, imo it would probably be a good idea to mention it anyway since I will probably not know.
PS: Everything is backed up in case something goes wrong so I'm ready to experiment as needed.
This isn't a time sensitive goal either so by all means take your time during this discussion.
Click to expand...
Click to collapse
Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
TWRP: https://forum.xda-developers.com/t/...310ww-mt6765-android-10.4163497/post-84082633
File download: TWRP3.5.0_10 BLU G90 PRO
You need 1 more file vbmeta modified too but I can put that after if you want TWRP or stock boot.img if you try magisk manager.
lopestom said:
Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
TWRP: https://forum.xda-developers.com/t/...310ww-mt6765-android-10.4163497/post-84082633
File download: TWRP3.5.0_10 BLU G90 PRO
You need 1 more file vbmeta modified too but I can put that after if you want TWRP or stock boot.img if you try magisk manager.
Click to expand...
Click to collapse
So i want to root my Blu G90 Pro but have no idea how to do it, If you could teach me that would be helpful XD
YungGravity said:
So i want to root my Blu G90 Pro but have no idea how to do it, If you could teach me that would be helpful XD
Click to expand...
Click to collapse
If you haven't unlocked your bootloader already, press build number 7 times in about device, go to Dev settings, enable USB Debugging, enable OEM Unlocking, go to fastboot, type: fastboot flashing unlock, press volume up button. Make sure to enable Dev settings again and enable USB Debugging again when the phone resets after you unlock the bootloader.
Download WwR_MTK 2.30 and SP Flash - version 5.2112 would be best. Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G90 Pro is MT6785. Click create and save as and make sure to save the files in one folder like I did. Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it. Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0, make sure to get the Start Address and the value address then add the start and value address. Then power off the phone and press readback, then open Wwr_MTK and add the ROM-0. Then go to search of partitions, then find boot and copy the start and value address. Go to SP Flash, go to readback, add the start and value address. Then power off the phone and press readback. Then install Magisk Canary on the phone, patch it and press patch vbmeta image. Then flash it over fastboot. Then you have a rooted BLU G90 Pro.
ATBG said:
To root it, use this website to download the stuff you need: {Mod edit}
Click to expand...
Click to collapse
@ATBG I've removed the link from your above post. The site you'd linked is not only a phone related site but also a commercial website e.g. providing paid courses.
XDA Forum Rules (excerpt):
11. Don’t post with the intention of selling something.
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:
A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.
B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
Click to expand...
Click to collapse
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay-per-click links, all forms of crypto-mining and other income generating methods are forbidden. Do not use XDA-Developers as a means to make money.
(However, hosting sites that provide a small amount of income, are GPL compliant, have direct download links, and minimal ads are allowed contingent on XDA approval.)
Click to expand...
Click to collapse
Regards
Oswald Boelcke
Senior Moderator
YungGravity said:
So i want to root my Blu G90 Pro but have no idea how to do it, If you could teach me that would be helpful XD
Click to expand...
Click to collapse
If that doesn't work, download the stock firmware from XDA. Then flash vbmeta --disable verification then flash boot.img.
ATBG said:
If you haven't unlocked your bootloader already, press build number 7 times in about device, go to Dev settings, enable USB Debugging, enable OEM Unlocking, go to fastboot, type: fastboot flashing unlock, press volume up button. Make sure to enable Dev settings again and enable USB Debugging again when the phone resets after you unlock the bootloader.
Download WwR_MTK 2.30 and SP Flash - version 5.2112 would be best. Open WwR_MTK 2.30 and create a basic Scatter File by choosing the Platform Type (processor) which for Blu G90 Pro is MT6785. Click create and save as and make sure to save the files in one folder like I did. Open SP Flash Tool and under the download tab choose the scatter file we just created it will have only Preloader under it. Go to the Readback tab press Add -- Double click on what was added and just keep it saved as ROM_0, make sure to get the Start Address and the value address then add the start and value address. Then power off the phone and press readback, then open Wwr_MTK and add the ROM-0. Then go to search of partitions, then find boot and copy the start and value address. Go to SP Flash, go to readback, add the start and value address. Then power off the phone and press readback. Then install Magisk Canary on the phone, patch it and press patch vbmeta image. Then flash it over fastboot. Then you have a rooted BLU G90 Pro.
Click to expand...
Click to collapse
Atbg can I message you for some help with the rooting of this blug90 pro?