I unlocked my bootloader a month before and I didn't know how to relock it back so I searched and found this website >>androidgadgematic I followed everything it mentioned and after finished installation, I hold on the boot button, the green light indicator blinked once and vibrated once but after that gave no respond. I didn't unroot my phone before doing the relock procedure. Now, I really don't know what to do because I searched google but none. I indeed need a step by step procedure to save my phone. How to boot my phone now, or else it is dead. I don't have if any method to reinstall ALL system files, no matter kernel, firmwares via my pc as long as it can helo my phone to boot up.
How to restore the stock bootloader on a HTC phone?
I explain: after the root process, made with the Revolutionary tool, the bootloader isn't the same as before: now there are some lines i don't like (especially the one that allows to format the phone only by pressing two or three buttons). Is there a way to change the bootloader, and back it up, or if i lose the phone, the "volume down-power button trick" could make a new phone?
I tried everything, including a method of mine to set the s-on and using the ruu, but nothing changed.
Yesterday I got a sort-of-refurbished Nexus S (I9023) which was apparently not in such a good shape...Had problems flashing the system and userdata partitions (kept saying they were flashed fine but after reboot went back to their previous state).
I followed some tip without actually reading up on it and ended up formatting my bootloader partition.
Now, what I get is just a black screen no response or anything but using a tool called UnBrickable Mod I can get it back to fastboot mode and then boot into a recovery image and have adb access.
All in all, I am currently stuck cuz I want to flash a new bootloader image but what i get when i do that is:
Code: ~ # nandwrite /dev/mtd/mtd0 /bootloader.img Skipping bad block at 0x00000000 Skipping bad block at 0x00040000 Skipping bad block at 0x00080000 Skipping bad block at 0x000c0000 Writing at 0x00100000 Writing at 0x00140000 Writing at 0x00180000 Writing at 0x001c0000 nandwrite: not enough space in MTD device
I have read that NAND blocks tend to go bad when continuously being flashed, but 50% bad blocks on the bootloader partition? Seems pretty unlucky... Is it possible to resize the partitions without any JTAGing or writing custom bootloaders?
Can anyone give me some insight on restoring an Eris completely back to stock? I was running 2.1 OTA rooted and I'm trying to get the stock recovery back. I rolled it back to 1.5 using the SD card method, downloaded the OTA 2.1 update but it won't install since the bootloader is S-OFF. Is there an SBF that I should use for this that gives me a total stock flash? I tried to re-root and start over but I wasn't able to get SU installed...I'm all twisted around here and could use a back to basics walk through if one exists.
I have a Nabi 2 that was rooted almost a year ago to gain access to the Google Play store.My needs have changed since then and I wanted to restore it to factory settings.
If I boot normally the Nabi is stuck here:
I have managed to get it to boot to TRWP by pressing the power and + keys. I see this:
There are no images to "restore" under the restore tab. This is what I see:
provide me with a kernel file or some tips on how to restore the machine to it's 'out-of-the-box' configuration. I want to donate this device to a young child and need to get it back into a kid friendly mode.
Anyone else had abny issues with the back up restore function? I tried to do a software update, to which something seems to have happened. All i can see for the time being is an update to the virtual keyboard. Anyway, lost apps, contacts etc, so went into the menu on the handset and selected back up, restore. Restored numbers etc to phone book and over 150 number details are missing. The back up utility doesn't seem to have backed up all my numbers. Also, any personal photo's of callers etc have either vanished or the photo's are now against the wrong people. So much for this back up service, it's going to take hours, if not days to try to get the phone back tot he way it was!
since I own a Neo V which is locked, and the service menu in the phone says that the Bootloader cannot be unlocked. if I unlock my SIM lock(probably with TurboSIM, since thats the cheapest solution), would that enable me to unlock my bootloader, and start the real modifying of my phone?
The size of the file is much smaller than the size of the stock bootloader, but I don't know if it matters or what exactly I need to flash. I did a lot of web search, including here on XDA, but found no evidence of struggling with flashing the bootloader.
My Lava Mtab MG7 has become locked due to too many wrong pattern attempts. I can't log into the Google account to unlock it. I wanted to enter recovery mode to wipe data (hard reset). But I don't know the combination of key presses to enter the bootloader. I have tried the following:
1. Vol Up + Power 2. Vol Down + Power 3. Vol Up + Vol Down + Power
I've been following the instructions on the HTCdev website for unlocking the bootloader on my HTC sensation XE. Ive made it to the last step and acquired the unlock code from HTC. I then copied that to my computer and followed the last step "fastboot flash unlocktoken Unlock_code.bin" but I get an error message in the CMD promt "remote: unlock token check failed"
I have made sure that the .bin file is in the correct directory (c:Android).I have USB debugging enabled and fastboot disabled.
i want to know if it's possible to root an Android without unlocking the bootloader. My problem is I don't want anything wiped off the phone. I'm trying to get past the lock screen, because I found this phone in the street, so I want to get the numbers in it to try and return it. I've heard you can bypass the lockscreen if it's rooted. It's a Samsung Galaxy S Mesmerize, (or Fascinate).
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
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 successfully unlocked the bootloader on my xperia x8 via flashtool put on custom kernel nAa 14 and miniCM7 Yay.Everything is fine apart that I want to change network because they have much better deals etc.I went to the 3 network shop and tried to put in the Sim, it took it in loaded but wouldnt register with the network , in fact I tried last week when I was on stock kernel and gingerxperia and it asked for ''unlock code'', today it didn't ask for unlock code took it in but wont register.I guess there must be some sim lock or something.
Maybe it is unlocked but something to do with Radio pehaps nonetheless my current Network works fine.here's my S1 LOG if any good. after unlocking BL of course
Welcome to S1 identify tool 16/09/2012 17:16:15 16/09/2012 17:16:15 TO CONNECT NEXT PHONES [code]....
So I made the mistake of attempting to root my new HTC one V without knowing what I was doing. I currently can't get past the bootloader screen. I've attempted installing the RUU for my phone with no success. I've resorted to extracting the rom.zip from the RUU, renaming it PK76IMG.zip (required for hboot to recognize it) and putting it on my sd card. Everything works fine up until the end when it says "hboot version is older! Update failed"
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?