Related
Notice this could hose,break,trash or brick your phone. You are warned.
Update
Thanks to both CVPCS and Dragonzkiller and the DX2-Dev-Team. And of course thanks to koush. And Tenfar too did he did find the /preinstall hack? Did Dragonzkiller fixed the graphics or what? IDNK, it is fixed(/sbin/recovery in DK, cvpcs is broken). Hence the hybrid zip.
The UL zip works some what from /preinstall see my thread. http://forum.xda-developers.com/showpost.php?p=20634404&postcount=1 It may do the same if flashed via Tenfars,our bootstrap, just flash it as you would any zip and it will take over.
It backs up and will restore, from adv restore, /cache and(if set in recovery.fstab) sd-ext. A full restore bombs:
Checking MD5 sums...
cache.ext3.tar: OK
data.ext3.tar: OK
system.ext3.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-01-02.05.08.01//system.ext3.tar
Restoring system...
E:format_volume failed to unmount "/system"
Error while formatting /system!
Other features may work. I find that zipping from win7 winrar fails but Root Explorer zipping results work.
/sbin/recovery is distorted (main screen):
https://github.com/cvpcs/DroidX2Bootstrap/tree/master/assets
Distortion fixed;
https://github.com/DX2-Dev-Team/DX2-CWMR/tree/master/assets
Edit What is the "/preinstall cwr hack"?
TO PUT IN PLAIN TERMS : ALL YOU NEED FOR ANY CHARGE ENABLED RECOVERY:
THE FILES: "hijack" AND (THE HACKED) "charge_only_mode" IN /system/bin
AND ".revovery_mode" IS IN /data
YOU DO NOT NEED ANYTHING ELSE BUT TO LOAD /preinstall
WITH YOUR FAV RECOVERY NAMED: "update-recovery.zip", ALONG WITH IT'S BINARY (SAME AS INSIDE THE ZIP/meta-inf....) CALLED: "update-binary" AND "hijack" (SAME AS ABOVE). Thats it! 6 files. With permissions- See above link.
Older post
5.0.2.0 http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip
Not everything works: when flashing between recoveries they need to be on internal sd, and, of course, backup and restore may work but its for ul bootloaders only.
DO NOT FLASH FROM ROM MANAGER. IT WILL BE SBF time.
Flash from tenfars and keep a copy of both on int sd (tenfars update-recovery.zip and the DL) to go back and forth. Do not backup and restore with this.
Just checked out the updater script and it looks like it should work, barring no needed changes on the scripts in sbin that it copies. I wonder if ADB works in it on this one. This could be a huge bonus for what were trying to do since BSR is kinda old and crappy
No adb in adv menu.
skwoodwiva said:
No adb in adv menu.
Click to expand...
Click to collapse
ADB shouldnt be in a menu. Should just be enabled by default. Course it only would work if it was plugged into a computer at the time you dropped into CWR. It doesnt support USB state changing.
So if the cwr in charge mode triggered, as is the preinstall hack, then no adb?
Log from cwr
init.svc.battd running
.usbd running
.touch stopped
.atvc stopped
.adb running
Extended commands not found.
See if you can run any adb commands like:
adb devices
adb pull /system/build.prop
etc...
It fails to mount sdcard. When recovering or manual mount.
I'm done messing this one.
I was able to overwrite the one in /data/data/tenfar folder but not in /preinstall folder anything special I need to try? Still went into BSR when I rebooted to recovery.
Sent from my DROID X2 using XDA App
I am learing as I go, but the point I realized is when you go to adv menu,in cwr,and reboot recov the current cwr gets loaded to /preinstall. So paste to data/data...files run sr then do reboot recov. Then paste to preinstall.
Cool ill give that a shot thanks!!!
Sent from my DROID X2 using XDA App
If I had the knowhow I would hack the garphics from 5010atrix to 5025x2!! .
But why would the newest Dx2 be any good and NOT a failure and be so messed for all this time? Unless one failure hides the other.
It probably can't mount SD due to a wrong mountpoint in one of the scripts. Should be easy to fix.
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip
newer atrix 5020 all works but restore fails as boot img, of course, won't load.
skwoodwiva said:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip
newer atrix 5020 all works but restore fails as boot img, of course, won't load.
Click to expand...
Click to collapse
how hards that going to be to fix?
Ha ha ha ha!
You got me!
But it easy to flash between these cwrs even back to tenfars. Want to find a way to recwr after a wipe or flash.
The skewed graphics problem is from within the recovery (binary) in /sbin of the
zip: http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.5-daytona.zip .
I pasted the file from the above into this http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.zip and got same graphics skewing.
balltongue said:
See if you can run any adb commands like:
adb devices
adb pull /system/build.prop
etc...
Click to expand...
Click to collapse
Is this from android/sdk in win7?
Can you give me a prep? I am just a NooB.
Within your sdk folder look for platform tools, adb is within this folder. Navigate to platform tools directory using cmd then enter the commands.
Sent from my DROID X2 using xda premium
skwoodwiva said:
Is this from android/sdk in win7?
Can you give me a prep? I am just a NooB.
Click to expand...
Click to collapse
I pm'd you with some info about setting up sdk.
Here is a complete guide for anyone interested in rooting the HTC Droid DNA. The insecure boot image, TWRP recovery, CWM recovery and SuperSU files used in this guide are not my own developments, and their developers have been credited in the end of this post.
I am only writing this as a newbie-friendly guide for everyone, and am providing my own SuperSU, su and busybox installer zip file that includes everything you need for full root.
Unlock the bootloader of your device by visiting the HTC bootloader unlock page. Warning: This will wipe your data.
UPDATE: Thanks to Verizon, the official bootloader unlocking method mentioned above no longer works. Please refer to this method for unlocking the bootloader.
Download ClockworkMod or TWRP recovery for the device and rename it to recovery.img (or keep the existing name and change recovery.img in the command below to that name).
Download the SuperSU and busybox package and put it on your SD card.
Put your phone into bootloader mode and connect it to your PC via USB.
On your computer, make sure you are in the folder where you downloaded the recovery file and use this command to flash the recovery:
Code:
fastboot flash recovery recovery.img
Finally, reboot your device into recovery, flash the SuperSU and busybox package and reboot your device.
You should now have root access.
Credits:
jcase for unlocking the bootloader after Verizon decided to lock it.
dsb9938 for sharing the CWM port and correcting me regarding my previously posted and now removed second method involving his insecure boot image
Dees_Troy for TWRP recovery.
utkanos for CWM port.
Chainfire for developing SuperSU
I have tried to credit everyone involved but if I have missed out on anyone, please do let me know.
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
hotmonkas said:
thanks for the guide!
just one question though. when you say "Download the SuperSU and busybox package and put it on your SD card.", what do you mean exactly by SD card? doesn't the DNA not have a SD card? sorry if this is a dumb question. i've never rooted a phone before :/
Click to expand...
Click to collapse
Internal storage would be another name for the SD card.
touretts69 said:
Internal storage would be another name for the SD card.
Click to expand...
Click to collapse
ah okay, thank you
which device do u use on the htc page?
nyjw said:
which device do u use on the htc page?
Click to expand...
Click to collapse
"Other devices", or similar.
Sent from my ADR6425LVW using xda premium
Awesomeness.
The fact that this phone is rooted a week before its even out... simply awesome. I love XDA!
So excited for this phone.
HQRaja said:
Code:
adb shell mount -o remount,rw /system
[LIST=1]
[*] adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
[*]Reboot your device.
[/LIST]
Click to expand...
Click to collapse
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
dsb9938 said:
This will not work. You cannot write to /system except in recovery.
This is why I did not publish my initial root method. Using a package and flashing in recovery is the only way to get files on /system without some really gnarly stuff.
D
.
Click to expand...
Click to collapse
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
HQRaja said:
Thanks for your response. =)
Based on my understanding (and my experience with Nexus devices), once you boot using an insecure boot image, you have full root access in ADB since it is running adbd as root on the device. You can then successfully write to the /system partition and the changes persist after reboot. While I can confirm that the above will work on any Nexus device as well as any similar device with an unlocked bootloader and fastboot access, I am not 100% sure if that's how it works on HTC devices that have the S-ON flag. Are you referring to S-ON devices in particular here?
Click to expand...
Click to collapse
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
dsb9938 said:
Normally it does work that way. And I was very disappointed that it did not on this phone, as I made the kernel just for that reason.
I think there was an error in the coding where it tells unlock which partitions to remove write protection from. That, or they just wanna make our lives hard for some reason.
Either way, you cannot write to /system while the phone is booted normally without S-Off. Even as root.
D
.
Click to expand...
Click to collapse
Ah I see. Thanks for pointing that out. I'll remove the second method from my guide, since including that would be pointless if that's the case as you can now confirm.
So does this method work? Or not???Im confused with the last few posts. Thanks
suzook said:
So does this method work? Or not???Im confused with the last few posts. Thanks
Click to expand...
Click to collapse
Edited post is fine. He removed the part I was talking about.
D
.
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Irish65 said:
What I want to know most if anyone knows..will the DNA through verizon be unlockable....I'm actually using the RAZR Maxx hd through verizon and Motorola has restricted unlocking the bootloader because of verizon
Sent from my DROID RAZR HD using xda app-developers app
Click to expand...
Click to collapse
You can't do any of this stuff without unlocking.
As of right now, it is working.
D
.
How do you do the command in the folder were u downloaded to like the instructions say?
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
Please be more specific.
D
.
idle0095 said:
How do you do the command in the folder were u downloaded to like the instructions say?
Click to expand...
Click to collapse
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
CastleBravo said:
In command prompt, use the "cd" command. The easiest way to do this is to make a folder at the root of your hard drive (C:\) and place all files you need to flash in here e.g. "C:\android\" Then in command prompt, type in "cd .." and press enter until it displays "C:\". Then type (if you use the same name as the example) "cd android" and it will enter the folder "C:\android\" where you placed the files. Now you can continue with the rest of the guide.
Click to expand...
Click to collapse
Or if on Windows, simply: Do the following in folder where files are located.
Shift+Right-Click > Open Command Window Here
I've never had an HTC device before but does using the HTC bootloader unlock is that making it s-off? Also I don't see the DROID dna on the list
Sent from my SCH-I535 using xda premium
I am running stock DNA, rooted, and with CWM touch recovery. For myself, being root is not merely a luxury, it is a need. Most importantly, I cannot stand having a crippled unix terminal without busybox, which of course, requires root.
I know not what the imminent OTA will bring, but root is too precious to risk losing. I would therefore like to engage in a DNA-specifc discussion about disabling the OTA update.
From what I can tell so far, the two methods include:
1) renaming the otacerts.zip file in /etc/security to a .bak file. This will not work in the present case, since /etc is mounted at /system/etc, and /system can only temporarily be mounted rw due to us being stuck with "S-ON" for now.
2) installing "FOTAkill.apk", or, flashing its corresponding zip (attached below) in custom recovery. Again, in the present case, this file was written for the EVO, and will most certainly not work. The updater-script in the zip can be modified to reflect the correct mount points, but there is a corresponding binary which I have no clue contains what, and would certainly need some expert opinion about.
Any ideas ye fine fellers?
You could always do load ota root keeper from the market back your root up temp un root via app update ota and then re root using the app, I have done this on other devices and I never lost root. Worked well. Might be worth a shot.
Sent from my HTC6435LVW using xda app-developers app
manzdagratiano said:
I am running stock DNA, rooted, and with CWM touch recovery. For myself, being root is not merely a luxury, it is a need. Most importantly, I cannot stand having a crippled unix terminal without busybox, which of course, requires root.
I know not what the imminent OTA will bring, but root is too precious to risk losing. I would therefore like to engage in a DNA-specifc discussion about disabling the OTA update.
From what I can tell so far, the two methods include:
1) renaming the otacerts.zip file in /etc/security to a .bak file. This will not work in the present case, since /etc is mounted at /system/etc, and /system can only temporarily be mounted rw due to us being stuck with "S-ON" for now.
2) installing "FOTAkill.apk", or, flashing its corresponding zip (attached below) in custom recovery. Again, in the present case, this file was written for the EVO, and will most certainly not work. The updater-script in the zip can be modified to reflect the correct mount points, but there is a corresponding binary which I have no clue contains what, and would certainly need some expert opinion about.
Any ideas ye fine fellers?
Click to expand...
Click to collapse
There are system writable kernels out there, and you can always rename your files in recovery. S-Off is not an issue in this scenario.
delete checkinprovider.apk, cotaclient.apk, and updater.apk from /system/app
Jaggar345 said:
You could always do load ota root keeper from the market back your root up temp un root via app update ota and then re root using the app, I have done this on other devices and I never lost root. Worked well. Might be worth a shot.
Click to expand...
Click to collapse
I have indeed heard this alternative thrown around but I am not willing to chance it; I have seen an equal amount of horror stories about people having their systems fried with this method (the Droid X for instance, which I had and where the last update broke root).
SolusCado said:
There are system writable kernels out there, and you can always rename your files in recovery. S-Off is not an issue in this scenario.
Click to expand...
Click to collapse
I will look at what's out there and if it is stable enough to be flashed. How does one rename files in recovery though? I rebooted into CWM (touch) and I see no such option - unless you can remount a partition and rename files in it somehow.
nitsuj17 said:
delete checkinprovider.apk, cotaclient.apk, and updater.apk from /system/app
Click to expand...
Click to collapse
This avenue seems promising. Has anyone tried this before? Also, how does one delete these in the S-ON situation? (I'm assuming recovery is the answer). I feel if I remounted rw, deleted and then rebooted, they will be right back where they are.
manzdagratiano said:
This avenue seems promising. Has anyone tried this before? Also, how does one delete these in the S-ON situation? (I'm assuming recovery is the answer). I feel if I remounted rw, deleted and then rebooted, they will be right back where they are.
Click to expand...
Click to collapse
If you install a kernel with /system writing enabled you can just delete them normally.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you install a kernel with /system writing enabled you can just delete them normally.
Click to expand...
Click to collapse
Great... thanks! I am looking into custom kernels. By the way, if custom kernels that do allow write to /system can be concocted, why is S-ON an issue at all? I was under the impression that this has to do with NAND memory being inaccessible, which seems to be a lower level issue than the kernel.
manzdagratiano said:
Great... thanks! I am looking into custom kernels. By the way, if custom kernels that do allow write to /system can be concocted, why is S-ON an issue at all? I was under the impression that this has to do with NAND memory being inaccessible, which seems to be a lower level issue than the kernel.
Click to expand...
Click to collapse
With s on we can not.
Flash radios
Flash kernels in recovery.
Change the splash screen
Go back to a locked bootloader
And a few other things I'm probably forgetting.
Sent from my HTC6435LVW using xda app-developers app
I used to have a copy of Hasoon's tool, but I reformatted my PC a while ago and no longer have it.
I have a replacement for my son's broken phone, but I can't get it rooted or even install recovery because I get the Main Version is older error. I used to just use the tool, but all links to it have been removed from everywhere I can find. Is there anything I can do to get that back?
ncwildcat said:
I used to have a copy of Hasoon's tool, but I reformatted my PC a while ago and no longer have it.
I have a replacement for my son's broken phone, but I can't get it rooted or even install recovery because I get the Main Version is older error. I used to just use the tool, but all links to it have been removed from everywhere I can find. Is there anything I can do to get that back?
Click to expand...
Click to collapse
It is so simple to root the Rezound, there is no real need for an all in one tool just remember that it will wipe the phone...
1) Download the latest SuperSU.zip from here: http://download.chainfire.eu/supersu and place it in the root of the SD Card
2) Unlock via HTCdev (instructions are all over the place, including at HTCdev.com) and verify booting and operation
3) Extract recovery.img from the latest TWRP package and place in adb directory
4) Boot into Hboot and then start Fastboot
5) Execute "fastboot boot recovery.img"
6) Install/Flash SuperSU.zip from Step #1
7) Reboot
Done... That's it, your rooted and no MainVer issues!
Although, I would keep it stock until it OTA's to the latest version... unless it is already 4.5.605.14, then you have to do it the way I mentioned, the all in one tool won't work due to Hboot being to new.
To add; you may want to install busybox as some root apps need it. Its simple as getting Stericson's BusyBox app and pressing install then rebooting.
Sent from my Rezound using Tapatalk 4
3) Extract recovery.img from the latest TWRP package and place in adb directory
Does this mean create an adb folder on root of SD? What else should be in it? Sorry, not a noob just been a while since I rooted and I have to root\s-off a replacement. Thanks!
tholmes8291 said:
3) Extract recovery.img from the latest TWRP package and place in adb directory
Does this mean create an adb folder on root of SD? What else should be in it? Sorry, not a noob just been a while since I rooted and I have to root\s-off a replacement. Thanks!
Click to expand...
Click to collapse
No... On your computer you should have installed ADB (Android Debug Bridge), this is what gives you the adb.exe and fastboot.exe files to talk to the phone and perform operations from your PC... The directory that contains these files (usually .\adb\platform-tools\) is where you copy this file... These commands are done on your PC and the recovery.img is pushed to the phone.
There are tons of guides on this that are literally step by step, even Youtube videos, no offense, bur if you don't comprehend some of these steps you might want to do some more research before continuing.
Sent from my Nexus 4 using Tapatalk
acejavelin said:
No... On your computer you should have installed ADB (Android Debug Bridge), this is what gives you the adb.exe and fastboot.exe files to talk to the phone and perform operations from your PC... The directory that contains these files (usually .\adb\platform-tools\) is where you copy this file... These commands are done on your PC and the recovery.img is pushed to the phone.
There are tons of guides on this that are literally step by step, even Youtube videos, no offense, bur if you don't comprehend some of these steps you might want to do some more research before continuing.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
No offense taken. Been brushing up and weeding out stuff that is out of date. I did install updated ADB/SDK and go over the guides. All coming back to me now. Think I've got all I need now. Thanks for the reply.
tholmes8291 said:
No offense taken. Been brushing up and weeding out stuff that is out of date. I did install updated ADB/SDK and go over the guides. All coming back to me now. Think I've got all I need now. Thanks for the reply.
Click to expand...
Click to collapse
OK, cool. If you need more assistance, fell free to ask.
Just for future reference... avoid the "one click" tools, especially on the Rez, they are mostly out of date. Plus knowing how to do it manually is usually quite useful.
acejavelin said:
OK, cool. If you ne. more assistance, fell free to ask.
Just for future reference... avoid the "one click" tools, especially on the Rez, they are mostly out of date. Plus knowing how to do it manually is usually quite useful.
Click to expand...
Click to collapse
Yeah I don't use 1 click. Thanks for the offer
Recently I was studying android recovery mode, and I have some questions. Anyone knows the answer? Thanks very much.
1. Can recovery flash bootloader?
From this link====>http://forum.xda-developers.com/showthread.php?t=2321310, I think it can do that. But I'm not sure.
2. Can recovery flash recovery partition itself?
I think it can not do this. Not confirm that.
3. We know in update.zip, boot.img is corresponding boot partition, but why system is a folder, not system.img? There is a system partition also.
4. While OTA upgrade system, why the update package downloaded under /cache path? Can we change it to sdcard?
5. Most important, what exactly update-script do things under recovery mode? How the command executed?
BTW, there are other questions, but not related to Recovery Mode.
1. How can I see the flash partitions? I know to use the command cat /proc/mtd, but as Samsung, it use emmc flash, while I type that command, no results printed. How to see?
2. About userdata partition, we know that when first run android OS, system will copy files from /system to /data, but does it do it every time that we turn on the phone or just do it once after the first booting after we update our system?
Hello,
I can answer some questions, and I hope someone else can fill the blanks.
1. Can recovery flash bootloader?
=> Yes, you have to modify your boot image, but it still possible, just include the modified boot image in the update file, and give good command in update.zip
2. Can recovery flash recovery partition itself?
=> I am not sure, but I think its possible, I saw code of recovery in Android code, so if you modify it, and include the good image in update.zip, I think you will see the modification. Never tried for now.
3. We know in update.zip, boot.img is corresponding boot partition, but why system is a folder, not system.img? There is a system partition also.
=> In fact is depend witch compilation system you use. For Cyanogen, yes in fact its a folder, but for AOSP its System.img
The difference comes from the command file in update, theire not the same. But finally the result in the same. We have a system partition.
4. While OTA upgrade system, why the update package downloaded under /cache path? Can we change it to sdcard?
=> Reasons I can see :
--> In past, sdcard was not mounted by default in recovery mode, so can't see the update.zip file
--> sdcard can be removed at any time, its dangerous, when do the update to loose the file
--> To be sure have right to remove the update.zip when installation done
--> Old phone didn't have all a sdcard, cache is sure to exists
=>Yes we can change it, but we have to be sure the sdcard is mounted on recovery mode. And be sure of the path of sdcard on recovery mode. For exemple in Nexus one it is /sdcard, in Samsung Galaxy S2 is /emmc/, in Samsung S4 mini its /sdcard/0/ ... So it could be a reason why its not in sdcard, because the path is not generic.
5. Most important, what exactly update-script do things under recovery mode? How the command executed?
=>It does lot of stufs, like mount partitions, copy system files, ...
The update-script is in elf script. Generally, an elf interpreter is given just next to the update-script.
I hope it helped you,
JHelp
1 yes, but flashing firmware from recovery can be dangerous and all though unlikely I have seen many brick there phone doing so
2. Yes, rather easily so long as the .zip is put together properly. But like bootloader, it is safest so flash through fastboot or download mode but a very unlikely brick so mostly safe
3. This is how a ROM gets built from source but it needs not be in this setup. At the same note I can't see a better way to flash through recovery than like it is. Using flash_raw_image would work but due to size a system.img shouldn't be flashed in recovery rather through fastboot, bootloader or download mode
4 mostly because you couldn't have an oem ota update without an SD card which isn't a prerequisite for using a phone. Also I believe there is some added safety flashing directly from nand, but in truth this is all speculation. Yes with a rooted phone this could be changed but most often it isn't wise to flash an oem ota on a rooted device
5 lots of things, take a look at my threads for a guide I made explaining this
1 cat /proc/partitions
mount
ls -l /dev/block/
And then keep searching until you get /by-name which many phones have, but this isn't always the same path so if you need further help ask and I'll walk you through it
2 I think this depends on a lot of things, but I don't have a good answer so rather than speculating I'll choose not to answer
Feel free to ask other questions
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
1 yes, but flashing firmware from recovery can be dangerous and all though unlikely I have seen many brick there phone doing so
2. Yes, rather easily so long as the .zip is put together properly. But like bootloader, it is safest so flash through fastboot or download mode but a very unlikely brick so mostly safe
3. This is how a ROM gets built from source but it needs not be in this setup. At the same note I can't see a better way to flash through recovery than like it is. Using flash_raw_image would work but due to size a system.img shouldn't be flashed in recovery rather through fastboot, bootloader or download mode
4 mostly because you couldn't have an oem ota update without an SD card which isn't a prerequisite for using a phone. Also I believe there is some added safety flashing directly from nand, but in truth this is all speculation. Yes with a rooted phone this could be changed but most often it isn't wise to flash an oem ota on a rooted device
5 lots of things, take a look at my threads for a guide I made explaining this
1 cat /proc/partitions
mount
ls -l /dev/block/
And then keep searching until you get /by-name which many phones have, but this isn't always the same path so if you need further help ask and I'll walk you through it
2 I think this depends on a lot of things, but I don't have a good answer so rather than speculating I'll choose not to answer
Feel free to ask other questions
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've got /by-num, but no /by-name, device is Sansumg GT-9288
not sure what a Sansumg GT-9288 is, gsmarena and google dont give me results
what happens with
cat /proc/partitions
or just
mount
?
demkantor said:
not sure what a Sansumg GT-9288 is, gsmarena and google dont give me results
what happens with
cat /proc/partitions
or just
mount
?
Click to expand...
Click to collapse
Sorry, type wrong, should be GT-9228, it's a customer made smartphone only for CMCC.
I can get the partition info by GT-9220, so I think it's because of the customer made that I can not get the by-name folder.
Thanks again.