Now that the mempodroid hack based on the memory leak discovered by Aedla has been blocked (since about kernel 2.6.42, and android 4.0.3), are there any remaining ways of getting root access without re-flashing the bootloader? Alternatively, any pointers to how I would find (or build) a bootloader for a tablet based on rockchip RK29 board (for which I'm unlikely to be able to get detailed documentation)? Or is there any way to downgrade the kernel without root access?
I rooted my S3 a few months ago based on some detailed instructions found online - no issues. The method used involved clockwork mod or some such.I was following these URL....
instructions to attempt to install liquid smooth (URL...) ROM. I had backed up everything on titanium backup and using the back up in ROM manager. In step 3.1, "flash a recovery image," I didn't think I needed to do this, as I thought it was a part of ROM manager.I proceeded onward, and after the phone finished making a back up, immediately after it started to install the new ROM, the screen went black (I assume the phone turned off).
I'm currently unable to get it to turn on at all, taking the battery out didn't do anything, and when I plug it into the comp via USB, it doesn't seem to recognize the device.I'm a broke med student on loans, and a new phone is going to hurt the bank account a lot.
From this link====>[URL] ....., 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?
I have an AT&T SGS4 with a melted USB port so there is no way for me to use fastboot or Odin to flash bootloaders, etc. Is it possible to flash a Samsung factory bootloader through recovery?
What I am trying to accomplish:
I am on Touchwiz 4.3 and the 4.4.2 KK release was leaked in our forum. I used the dsixda kitchen to break it down and made a ROM out of it that successfully flashed in recovery but kernel panics at the AT&T splash boot screen because the RAMdisk doesn't match the bootloader version. So I need to upgrade the bootloader to the 4.4.2 version so it will boot.
I unpacked the RAMdisk and there is nothing in any of the init.xx files that points to the bootloader. I even used a hex editor to look at the init binary which references the bootloader but there was nothing in there that I could change (from what I saw).
i recently broke my last phone, so i had it replaced and this one is running 2.3.6, i tried using that black white screen (cmd?) with the options ex:
1. unlock root etc.
2. CWM install/root etc etc. x. debugging etc
but no luck. When i reach the rsd lite portion of the first section, my phone just boots up into the os and rsd lite gets cancelled. ( i chose 2.3.4)when i first got it, i could do everything fine, but i couldn't boot after installing 3 different roms. but when i install clean software it works just as it should
Are there other ways to flash a recovery with a locked bootloader?
I can't flash my stock recovery through fastboot with a locked bootloader. I can't boot into my recovery because my current recovery is TWRP 18.104.22.168 and I have a locked bootloader. I can't unlock my bootloader because I have used an IMEI Hack Tool and set my IMEI to 0 (I guess). I can't boot into my ROM because I used an IMEI Hack Tool. I can't Force Upgrade too (Vol Up + Down + Power). It only shows a pink/purple screen.
I can only flash a recovery with an unlocked bootloader. I can only boot into a recovery with an unlocked bootloader (except for stock). I can only unlock bootloader if my IMEI has restored. I can only restore my IMEI if I can boot into my ROM. I can only boot into my ROM if I have a stock recovery. I can only Force Upgrade if I have restored my IMEI.
how to unlock boot loader, root and s-off my HTC one mini. I bought the phone in november so im assuming that i updated to 4.3 or it was already installed (relevant later). I htcdev unlocked my boot loader, installed twrp and made a backup, installed superuser and rooted my phone. Then I installed titanium backup pro, made a backup and uninstalled all the system apps/bloatware I didn't need. All was peachy but the apps kept reappearing which I found was down to s-on (despite what I read about htcdev unlock boot loader method making my phone s-off) . So I tried the revone method and got error 1 which apparently is down to having android 4.3 so I looked for an earlier ROM and flashed Magio r1 which worked fine but couldn't find the data/local/temp folder to install revone into. Probably could of put it somewhere else but I wasn't that confident with the s-off process. So I finally found Jmz m4 stock ROM so there was light at end of tunnel. So I read up on twrp factory reset/format data functions and saw people were using both methods. I went with the full format and factory reset afterwards. Looking back now that was pretty stupid as I have no ROM and no backups to restore to. I did manage to chmod 777 the permissions on my twrp backups and copy the to dropbox (after endless scouring of forums). I also know how to flash boot images and use the adb side load functions. I can't adb push the file as it returns with error closed, I've tried the following commands:
adb device - my device is attached and side loading. adb usb - returns error closed
adb kill-server adb start server - server starts successfully then returns error closed.
And just to be sure I tried with /data/media/, same error..I've fastboot flashed the jmzM4 ROM image and kernel but no joy as I'm guessing the boot image isn't enough and you need the zip. Currently I can load into boot loader and recovery no problem, just freezes on HTC load screen in normal boot up.
I was able to root the device by downgrading it but when i upgrade manually thru flashtool to ics 431,root and superuser app is gone.i also tried Root_with_Restore_by_Bin4ry_v16 but it does not show any restore backup option and nothing happens.. I read each and every related forum searched web but no luck .
Huawei ascend p1 B226 I was follow the steps to root my phone so that i can install CWM on the phone. But i cannot open fastboot/bootloader mode, i tried to use the command "adb reboot bootloader" to log into the bootloader mode but my phone was stuck at the logo. the device manager also show me an unknown driver "Blaze". i tried to install the driver "Blaze" into "adb bootloader interface" but when i check on"fastboot devices" i only get "? fastboot"
My phone wont boot into android because of a bad setting I made in pimp my rom, it only boots into recovery now. So what I need to do is sort files modified by a certain date and time (last night) and restore them with originals hoepfully to get my phone to boot back up.
So how do I navigate and search my root directory through 4ext recovery or bootloader, because those are my only options?
Is there a way to mount these directories and browse them through windows as if it were an actual folder so I can use windows 7's build in search features as well? I have android commander installed and can use that if need be.
how to exactly approach this without installing my rom back over again.
I have a One V, and I want to backup atleast 30 wifi passwords I have stored on my device, but all the apps on play store require root.I can't do that as unlocking the bootloader will remove my phone data, so I'm asking :
If I unlock the bootloader and then restore data still with the stock ROM on, will it restore the wifi data automatically, and then hopefully I can back it up with a wifi backup app (cause there is no way to root device without unlocking the bootloader atm)?Here's what dashboard is showing as backed up:
So I have a rooted Droid X running official 2.1. I want 2.2 but I want to keep my original bootloader. Is there an update.zip that can take me to the OTA or the leaked OTA without messing with my booloader or recovery? I would also not like to wipe my data ether.
I tried the 2.2 root process. short and sweet is downgrade 2.2 to 2.1. Bunch of command line stuff. Install usb drivers, open program to flash and it reboots the phone, then more command line stuff, then installs custom 2.2 and you are now rooted. I got to where I install the custom usb drivers and open the reflash program. All it does is go to the bootloader and sit there. I said screw it and was going to just reinstall 2.2 and be done with the attempt of rooting until a 1 click type came out. Problems is, now I cant even install 2.2. Sits at the bootloader screen. Called Sprint and they tried to help me do a factory reset by going to the phone app and typing ##87# or something.
When I hit reset it was supposed to show a screen thats wiping and reinstalling or something. Nothing happen. Stuck at that bootloader screen again. So here is what I think happened and I need help fixing it. I installed a newer bootloader or older one or something and the new 2.2 is having a hard time getting past it or I just completely screwed it all up. I am currently on 2.1 and all is working fine but I cant upgrade or anything. What are my options and how do I get this back to 2.2? Would love to try and root it and be done. Or just plug it into the PC and reinstall everything back to factory but I am coming from the iPhone where that is possible and I guess you cant on HTC.
how rooting works. I read that stock recovery doesn't let us flash packages not signed by the manufacturer, and that's the reason for custom recoveries (they don't check). So my question is how do we get recovery to flash the root package in the first place? Or is it the fact that I have a Samsung with an unlocked boot loader?