Develop Bugs

[TUT][HOW TO] Flash Recovey without use bootloader

Hi guyz! With this small guide I hope i'll explain to you how to flash a recovery without bootloader. C'mon!
1) Download the recovery
2) Extract the recovery image in the zip (normally the folder is named "pg76img.zip" and the recovery "recovery.img")
4) Download terminal emulator
5) Open Terminal Emulator
6) Write su and accept superuser request
7) write flash_image recovery /sdcard/recovery.img
8) if you'd like to try if recovery work write reboot recovery
9) enjoy!
-EDIT-
This script doesn't work with stock rom (sense roms)
Sent from my Wildfire S using xda app-developers app

This method won't work on Sense ROMs unless you install the flash_image script (Else you'll get not found or something similar).
Assuming you've already downloaded and installed Android SDK and that stuff, we can start:
1. Extract the script. Let's say you extracted it to your Desktop.
2. Connect your WFS with android debugging on.
3. Type the following:
Code:
adb root (enter)
adb remount (enter)
adb push Desktop\flash_image /system/bin (enter)
adb shell chmod 0755 /system/bin/flash_image (enter)
4. Flash your recovery. (In this case, your recovery.img is on /sdcard/)
Code:
adb shell flash_image recovery /sdcard/recovery.img
That's all. And there's no need to do this on CM-based ROMs as they already have this command script.

ScardracS said:
Hi guyz! With this small guide I hope i'll explain to you how to flash a recovery without bootloader. C'mon!
1) Download the recovery
2) Extract the recovery image in the zip (normally the folder is named "pg76img.zip" and the recovery "recovery.img")
4) Download terminal emulator
5) Open Terminal Emulator
6) Write su and accept superuser request
7) write flash_image recovery /sdcard/recovery.img
8) if you'd like to try if recovery work write reboot recovery
9) enjoy!
Sent from my Wildfire S using xda app-developers app
Click to expand...
Click to collapse
this won't work on stock roms....as stock doesn't have flash_image script....so mention in OP only for cm based roms....& ofcourse for stock based roms djoliver has already posted a tut

[TUT]How to flash a rom when your device boots in recovery or hboot.

You just want to flash a new rom... you did all the wipes and then you realize that you don't have any rom or nandroid backup on your sd card. ***! Don't worry bro. This is what you can do:
1. Search for a wonderful rom in the Android development section.
2. Download it and paste the rom.zip in the same folder where adb and fastboot are.
3. Go to Clockworkmod Recovery.
4. Go to mounts and storage.
5. You must see "unmount /sdcard/" and "unmount /system/".
6. open up command prompt and cd to your adb folder.
7. In adb, type: adb push romname.zip /sdcard/ where romname.zip is the name of the zip (you must have enough space left on your sd card).
8. Flash the rom and enjoy!
When you don't have Clockworkmod installed, do this:
1. Download the Clockworkmod recovery img.
2. Put it in your adb folder.
3. Open up command prompt.
4. Boot your device in hboot and connect it with the usb cable.
5. Cd to your adb folder.
6. In command prompt, type: fastboot flash recovery name.img where name.img is the exact name of the clockworkmod recovery img.
7. You just installed Clockworkmod recovery!
If this is too hard for you, flash an RUU.
Some tips:
1. Sometimes type: adb devices or fastboot devices.
2. Be sure you don't have a faulty usb cable.
3. For the lazy people, when you download a rom or recovery, name it to rom.zip or recovery.img
Hope this helped.

I will try this tonight. Any suggestions on ROM's for the MetroPCS CDMA Version? I'm on Android 2.3.4
ClockWorkMod Recovery 5.0.2.8

[ROM] Ubuntu touch 15.04 Vivid Velvet Attempt

Hi there everyone of the Sony xPeria Z Ultra forum.
I'll release here an Ubuntu touch Vivid Velvet Rom in the few hours.
I can't test it because I'm on android, also I won't test it yet by me because I cannot search for a recovery working for the Ubuntu.
So, I'll release the ROM with the cyanogenmod 11 boot.img
ROM Link:
http://d-h.st/NVOP
With the following adb and fastboot commands You'll need to type this on a Terminal:
Code:
sudo adb kill-server
sudo adb start-server
adb devices
adb reboot bootloader
then:
sudo fastboot flash boot boot.img (cyanogenmod 11)
sudo fastboot flash system system.img
sudo fastboot flash userdata userdata.img
After this, do this right ahead:
Code:
sudo fastboot reboot
Go to the recovery through the button sequence
Than install the armhf system preinstalled tar.gz file on it.
I hope that's work.
Please reply the issues even the working stuff here on this topic.
Thank You so much

this is Xperia ZL forum... Sure you are right here, cause you wrote Xperia z ultra?

I'll move it. I've noticed now.

[Guide] How to get partition table out of any phone using command prompt in windows

Here i can guide you to get the partition table details out of your phone.
Follow my steps seriously (don't ever miss or mess with any step. Just follow blindly. As I've faced same issue.
First of all take a Nandroid backup of your phone for safety.
Before going through any of these steps you need to install latest mi PC suite and MiFlash on your windows PC. As i am a mi [redmi 1s] phone user,i use pc suite and flash tool to install adb and fastboot drivers.
(If you are any other phone user, then you can get your phone compatible adb and fastboot drivers from google or you can use the universal fastboot and adb drivers).
here is the link to get universal adb and fastboot drivers for windows: http://forum.xda-developers.com/showthread.php?t=2588979
1) Connect your phone to your pc by using a compatible USB cable.
2) Now install Minimal adb and fastboot from here: (note the installation directory here)
http://forum.xda-developers.com/showthread.php?t=2317790
3) Next navigate to inside of installation directory (minimal adb and fastboot folder in my computer).
4) if you see adb and fastboot applications inside the folder then you are in the right directory.
Now by press and holding shift button make a right click inside the folder. Here you see open command window here, click on it. Or you can navigate to this folder through command prompt.
5) Now reboot your phone into fastboot by pressing volume button (in general down) and power button. if that doesn't work try by googling it.
6) Now in command prompt enter command
Code:
fastboot devices
.
If you see any device serial number <space> fastboot. if not wait a minute or two. for ex:
abbf287 fastboot
then your device is successfully connected in fastboot mode.
7) Now download the twrp recovery image file from twrp website. and select your device from devices and download the file by clicking the link with Recommended.
link: https://twrp.me/
8) And copy this file into the same folder as your adb and fastboot binaries (minimal adb and fastboot folder). Rename the image to twrp.img and type:
Code:
fastboot flash recovery twrp.img
press enter
Code:
fastboot reboot
press enter
9) Now to boot into your latest (twrp) recovery by pressing volume button (in general up) and power button.
10) Now in the same command prompt enter command
Code:
adb devices
.
If you see any device serial number <space> recovery. if not wait a minute or two. for ex:
abbf287 recovery
Then your device is successfullu connected in adb (recovery mode).
11) Now download the parted file from the link below and copy the file to the same directory where twrp.zip was copied.
link: https://drive.google.com/file/d/0B_IeQxB3hZfgbU93NzVOcWd6TjA/view?usp=sharing
12) Now in command prompt enter command:
Code:
adb shell mount -o remount,rw /system
13) Then enter next command
Code:
adb push parted /system/bin/parted
14) You should see some kind of push successful message. Then enter command:
Code:
adb shell
.
15) You should see a new command line host-name with a “#” sign next to it which indicates you’re connected as root user.
16)Now Enter the following command one after the other followed by enter.
Code:
chmod 0755 /system/bin/parted
Code:
parted /dev/block/mmcblk0
Code:
print
17) Now you have got a table. Which is the current partition table on your phone. Take screenshot of this details in maximized mode for future requirements.
Happy coding. And don't forget take Nandroid backup before messing anything.

ADB help

By Hashcode, Senior Recognized Developer on 1st February 2013, 10:57 AM over 5 years ago
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
with that being said here is what happens, i can see adb is working
C:\adb>adb devices
List of devices attached
B0CC060324930545 device
C:\adb>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
/system/bin/sh: su: not found
C:\adb>
I could go on on but, that would be more gibberish.
So, what is wrong? Did the commands change? Is my path set wrong on my pc? Is there a updated thread i just have not come across yet? Anyone?
I'll thank you now for any help

Nothing changed. If you get the device to show up with the adb devices command, then everything's theoretically set up. The only reason you're getting an error with su not being found is that you aren't rooted. Here's a quick way to get root (like actually super simple, considering you already have ADB working):
1) download the attached 8.1.4 bootloader file (this is ripped straight from my Kindle before I "upgraded" to 8.5.1 to test this out). you may consider placing it in the same folder as the adb program. Also download SuperSU and the latest TWRP build for this device.
2) shut down the kindle and make sure it's plugged in.
3) run fastboot -i 0x1949 getvar product, then power the kindle on. when you see "fastboot mode" on the kindle, you should see something in the command prompt that begins with "Jem". if you do, then it's working.
4) type fastboot -i 0x1949 flash bootloader jem_8-1-4_bootloader.img to flash the 8.1.4 bootloader. this is ESSENTIAL because the kindle won't boot custom (unsigned) images otherwise. more explanation below...
5) next, type fastboot -i 0x1949 flash recovery twrp.img, where twrp.img is the file name of the TWRP image you downloaded earlier.
6) type fastboot -i 0x1949 oem recovery to kick the Kindle into recovery mode. if all goes well, you should see "TWRP" on your device after a few moments.
7) copy the SuperSU zip you downloaded to the kindle's internal storage. then on the kindle, tap Install. Next, on the side menu to the left, swipe up from the bottom and tap "sdcard" (referring to the internal storage that you see on the computer when the kindle's plugged in). Tap the SuperSU .zip, and then swipe where indicated. Feel free to reboot the system, and then voila, you're rooted. You should be able to run those backup commands. As a bonus, you won't have to download TWRP or the bootloader image from that virus-laden d-h.st site - avoid it like the plague.
8) Because TWRP's already flashed, you can type adb reboot recovery from the stock OS to begin flashing a new ROM right away.
A couple side notes...
1) Because you've flashed TWRP, a custom recovery, there is no need whatsoever to run the stock recovery backup command. It's already been overwritten, and if you really need it (which, again, is highly doubted because it only lets you run a factory reset), you can actually extract the recovery image from the system partition. Just run adb pull /system/recovery-prod.img stock-recovery.img instead of the adb shell su... stock-recovery.img one.
2) You have to flash the 8.1.4 bootloader because the one you currently have is more than likely a newer version. Custom ROMs (and even recoveries like TWRP) rely on an exploit in the 8.1.4 bootloader in order to trick the device into running the image (and newer bootloaders have this exploit patched already). So technically, because the exploit has to be run every time, the bootloader is never "unlocked" - merely tricked. Without the older bootloader in place, you get what is referred to as the "red screen of death". It's not pretty, but it's not permanent either. (Just power off the kindle, and then run the fastboot command involving "getvar product" to get it to the bootloader so you can flash the 8.1.4 bootloader and go forward.)
Hope this helps!