Related
If you have any suggestions on making this guide better or to correct any mistakes I may have made please let me know.
This guide is intended for any Linux OS and includes detailed instructions. It should work with another Linux OS although I have only verified these steps using Ubuntu 9.10 aka Karmic. includes detailed instructions. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). It will cover the steps necessary to root, flash the new recovery image, create a full backup. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The linux file is called android-sdk_r06-linux_86.tgz. Extract the files to your home user directory so that you now have the folder /home/USERNAME/android-sdk-linux. Please note you must replace USERNAME with your own.
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to /home/username/android-sdk-linux/tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g DO NOT OPEN. Simply place this file in /home/username/android-sdk-linux/tools as well.
Step 4: USB Debugging should be disable before connecting your phone via the USB cable. Connect your phone and now enable USB Debugging.
Step 5: Open a terminal found under Applications>Accessories>Terminal
Step 6: You will now enter a series of commands which I will place in code boxes to indicate the entire command.
A.
Code:
cd ~/android-sdk-linux/tools
B.
Code:
sudo su
C.
Code:
./adb push asroot2 /data/local/
D.
Code:
./adb shell
E.
Code:
chmod 0755 /data/local/asroot2
F.
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#Now for a few last commands.
G.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
H.
Code:
cd /system/bin
I.
Code:
cat sh > su
J.
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
K.
Code:
exit
L.
Code:
exit
This will return the command line to ~/android-sdk-linux/tools.
M.
Code:
./adb push recovery-RA-heroc-v1.6.2.img /sdcard
N.
Code:
./adb shell reboot
This will cause to power off then back on automatically. Wait till the phone is fully booted to continue.
O.
Code:
./adb shell
P.
Code:
su
Q.
Code:
cd /sdcard/
R.
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
S.
Code:
reboot recovery
Step 8: This is the last command; You may now close the terminal. It will cause your phone to boot into recovery mode; it should take no longer than 30 secs.
The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!
[email protected]:/home/lepri/android-sdk-linux/tools# sudo su lepri
[email protected]:~/android-sdk-linux/tools$ su root
Password:
[email protected]:/home/lepri/android-sdk-linux/tools# /adb push asroot2 /data/local/
bash: /adb: No such file or directory
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb push asroot2 /data/local/
828 KB/s (74512 bytes in 0.087s)
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ chmod 0755 /data/local/asroot2
$ /abd shell
/abd: not found
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/493/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/bin
# cat sh > su
# chmod 4755 su
# exit
$ exit
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.2.3.img
Thanks for guide but I dont think it worked for me, HTC logo stays on but thats it... have to pull out battery to start the phone phone works but no joy with recovery image ((
I have HTC hero with sim(If this info any use to you)
lepri13 said:
[email protected]:/home/lepri/android-sdk-linux/tools# sudo su lepri
[email protected]:~/android-sdk-linux/tools$ su root
Password:
[email protected]:/home/lepri/android-sdk-linux/tools# /adb push asroot2 /data/local/
bash: /adb: No such file or directory
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb push asroot2 /data/local/
828 KB/s (74512 bytes in 0.087s)
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ chmod 0755 /data/local/asroot2
$ /abd shell
/abd: not found
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pipe_inode_info layout
Opening: /proc/493/fd/3
SUCCESS: Enjoy the shell.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/bin
# cat sh > su
# chmod 4755 su
# exit
$ exit
[email protected]:/home/lepri/android-sdk-linux/tools# ./adb shell
$ su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.2.3.img
Thanks for guide but I dont think it worked for me, HTC logo stays on but thats it... have to pull out battery to start the phone phone works but no joy with recovery image ((
I have HTC hero with sim(If this info any use to you)
Click to expand...
Click to collapse
You have a GSM HERO not a CDMA. This guide is intended for CDMA heros only.
Updated for recovery 1.5.1 image.
I keep getting the same error of insufficient permissions for device. What am I doing wrong? I disable USB debugging before I plug my phone in. Then I plug my phone in and enable USB debugging and then actually connect my mounting the SD card.
Edit: Ok. I found how to fix the insufficient permission problem...
Code:
./adb kill-server
sudo ./adb start-server
That will get your permissions correct but once I did that, I ran across a new error once I did ./adb shell the second time after the "chmod 0755".
Code:
[email protected]:/home/justin/android-sdk-linux_86/tools# ./adb push asroot2 /data/local/
711 KB/s (74512 bytes in 0.102s)
[email protected]:/home/justin/android-sdk-linux_86/tools# ./adb shell
$ chmod 0755 /data/local/asroot2
$ ./adb shell
./adb: not found
Whats wrong now?
I couldn't edit my post anymore but I found that it works if I just skip the second ./adb shell. It just caused problems for me because I was already in shell and was coming up with errors. I skipped it and my root smoothly after that.
Part I skipped...
You must replace username with your own actual username.
C. "./adb push asroot2 /data/local/"
D. "./adb shell"
E. "chmod 0755 /data/local/asroot2"
F. "./adb shell"
G. "/data/local/asroot2 /system/bin/sh"
For some reason the forums are letting me edit my posts. I know I'm wasting space but I would like to give credit to jnwhiteh for the ./adb fix. I searched for it and found it in a different part of the forums.
Problem flashing recovery
Thank you for the Howto.
I have no problem with the howto, until i try to flash recovery. It seems its going ok without error messages, but when i try to boot in recovery mode it does'nt work. Remains with the HERO logo in the screen and nothing happens.
Anyone can help me.
goshi0 said:
Thank you for the Howto.
I have no problem with the howto, until i try to flash recovery. It seems its going ok without error messages, but when i try to boot in recovery mode it does'nt work. Remains with the HERO logo in the screen and nothing happens.
Anyone can help me.
Click to expand...
Click to collapse
You're not giving the terminal enough time to flash the image probably. Give it like 10 secs to be on the safe side.
flash image not found
everything works fine up until i get to the part where you actually flash the recovery image, at which point i get an error reading : flash_image: not found
this is my code for the last part.
"[email protected]:/home/amills/android-sdk-linux/tools# ./adb push recovery-RA-heroc-v1.5.2.img /sdcard
1106 KB/s (3356672 bytes in 2.962s)
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell reboot
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell
# su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found"
goyanks said:
everything works fine up until i get to the part where you actually flash the recovery image, at which point i get an error reading : flash_image: not found
this is my code for the last part.
"[email protected]:/home/amills/android-sdk-linux/tools# ./adb push recovery-RA-heroc-v1.5.2.img /sdcard
1106 KB/s (3356672 bytes in 2.962s)
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell reboot
[email protected]:/home/amills/android-sdk-linux/tools# ./adb shell
# su
# cd /sdcard/
# flash_image recovery recovery-RA-heroc-v1.5.2.img
flash_image: not found"
Click to expand...
Click to collapse
is the phone fully booted when you run the flash_image command?
theresthatguy said:
is the phone fully booted when you run the flash_image command?
Click to expand...
Click to collapse
Yes, sense has booted up and everything, if this matters, my current recovery image is Amon Ra v1.2.3 and i had Eclair 2.1 v1.8 on it up until last night, as of now i have Fresh 1.1
If you're going to transfer the recovery image to the sdcard using adb push (as opposed to using usb-storage to drag/drop) you need to make sure that usb storage is turned off and the sdcard is mounted when you push the file.
My guess is that the sdcard wasn't mounted, and the file went to the (empty) /sdcard directory. Then when the sdcard is mounted, you can't see it. If you just reboot and do:
Code:
./adb shell
cd /sdcard
ls
does the recovery image file show up in the list?
I'm assuming that "flash_image: not found" means that the image file isn't where you're telling it to look.
buck2202 said:
If you're going to transfer the recovery image to the sdcard using adb push (as opposed to using usb-storage to drag/drop) you need to make sure that usb storage is turned off and the sdcard is mounted when you push the file.
My guess is that the sdcard wasn't mounted, and the file went to the (empty) /sdcard directory. Then when the sdcard is mounted, you can't see it. If you just reboot and do:
Code:
./adb shell
cd /sdcard
ls
does the recovery image file show up in the list?
I'm assuming that "flash_image: not found" means that the image file isn't where you're telling it to look.
Click to expand...
Click to collapse
no, it's there, when i tyle "ls", i get the following list returned.
Code:
# ls
2.1v1.8_heroc_7_signed.zip flashrec-1.1.3-20091107-2.apk
BetterTerm15.apk fresh-cdma-hero-1.1.zip
DCIM google_maps_navigation
HTC Sync media
LOST.DIR nandroid
Music prettybattery-googlecode-com
PicSay recovery-RA-heroc-v1.2.3.img
ToggleSettings recovery-RA-heroc-v1.5.2.img
Wallpaper rosie_scroll
aHome rssreader
albumthumbs tmp
aosp_heroc_20091217d.zip uloops
dolphinbrowser_gestures waze
furthermore, when i try to flash the recovery image now, i get no such error, instead I get a seemingly infinitely repeating series of "out of memory errors"
Code:
# flash_image recovery recovery-RA-heroc-v1.5.2.img
mtd: read error at 0x00000000 (Out of memory)
mtd: read error at 0x00020000 (Out of memory)
mtd: read error at 0x00040000 (Out of memory)
mtd: read error at 0x00060000 (Out of memory)
mtd: read error at 0x00080000 (Out of memory)
mtd: read error at 0x000a0000 (Out of memory)
mtd: read error at 0x000c0000 (Out of memory)
mtd: read error at 0x000e0000 (Out of memory)
mtd: read error at 0x00100000 (Out of memory)
mtd: read error at 0x00120000 (Out of memory)
mtd: read error at 0x00140000 (Out of memory)
mtd: read error at 0x00160000 (Out of memory)
mtd: read error at 0x00180000 (Out of memory)
mtd: read error at 0x001a0000 (Out of memory)
mtd: read error at 0x001c0000 (Out of memory)
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)
errors
I'm going to try rebooting the device and start from there. :|
this is bizzare, the first two times i attempted this (both times in Kubuntu 10.04 Alpha), i was able to flash the image with no trouble whatsoever.
------------------------------------------------------
i dont know what was up, fixed it and 1.5.2 is working great. thanks for the advice everyone. : )
problem :-(
Here's where I get to in the procedure, what's going on?
Code:
$ chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2 /system/bin/sh
$
Many thanks
David
swatsbiz said:
Here's where I get to in the procedure, what's going on?
Code:
$ chmod 0755 /data/local/asroot2
$ /data/local/asroot2 /system/bin/sh
[1] Killed /data/local/asroot2 /system/bin/sh
$
Many thanks
David
Click to expand...
Click to collapse
Do you have a non-Sprint hero? If say I recommend you check out the rooting a non-sprint hero thread.
Thanks so much for this great howto!
Looking down the road..... can the phone be unroot/restored from linux?
diordnahero said:
Thanks so much for this great howto!
Looking down the road..... can the phone be unroot/restored from linux?
Click to expand...
Click to collapse
After you flash a custom rom, no. You will need to RUU from a Windows box.
Doesn't work from a VM or from Mac Bootcamp either. Need to have a Windows-only craputer.
Hey all, new to xda. Hope I'm not asking stupid questions.
My friend gave me a Galaxy S to fix. Model: GT-I9003.
It has a boot loop problem, cycling the Samsung introduction animation (and sound first time round). The recovery mode didn't work to start with - also trapped in a boot loop.
I followed the instructions here (using Odin3 v1.85) and flashed XXKPE. It seemed to all work fine, but the boot loop remained. I booted it into recovery mode and the following error messages appear.
E:failed to mount /data (No such file or directory)
Click to expand...
Click to collapse
and under -- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p3
Click to expand...
Click to collapse
then
Data wipe failed.
Click to expand...
Click to collapse
From my research I believe it's a corrupted internal SD-Card and is fixed via parted? Could anyone go into more detail on how I would do this?
Many thanks.
I am facing a similar problem on my Galaxy SL... Need a solution too... I would appreciate any help...
Data partition has been corrupted, try flashing userdata.rfs with heimdall. A friend of mine had an stock/untouched phone and this happened to it, even with the corrupted partition i was able to boot cyanogenmod, and tried a lot of things, but nothing worked, it was on warranty, so i flashed back the original firmware and he took it to the service center.
If you want to try do this:
Flash bam kernel PDA_BCK_CF-root_universal_beta14fix.tar (http://forum.xda-developers.com/showthread.php?t=1355675)
Then from CWM flash cyanogenmod (i used cm7, but you can try with cm9)
after that the phone should boot into cyanogemod and give an error on the notification bar
extract the 6 files off the zip i attached and copy them to /xbin
from terminal emulator or adb shell run this for the 6 files:
Code:
chmod 0755 <file>
then run:
Code:
parted /dev/block/mmcblk0 mkfs ext2
When it asks for the partition number, enter 3
finally reboot, and if it worked you can flash a stock rom again, thats it, good luck
My phone boots up, but there are random reboots. Tried a lot of stock and custom ROMs... Nothing works... Warranty expired last week...
Thanks for your time. I appreciate it.
bruisedcrow said:
Thanks for your time. I appreciate it.
Sorry, I'm very new at this - my first hour doing this kind of thing. Could you explain the procedure in more detail - I would like to learn (make the best of a bad situation).
Am I right to say that the Bam Custom Kernel gives super-root level privileges? Allowing the CWM to fiddle with partions?
I've downloaded the normalboot.img for BCK. How do I flash this to my device? Could you link me to a tutorial?
EDIT: Alternatively could you point me to all the prerequisites I need to properly understand the problem and the methods required to fix it?
Click to expand...
Click to collapse
I tried that... My phone was booting up...
I have Android SDK on my PC... It includes some tools like ADB.
If your phone is rooted, you can use ADB to do things, like formatting...
Connected my phone. Booted into recovery. From Command Prompt, I went to ADB folder, then typed "adb shell". Then, typed in the parted command, and followed steps. Successfully done...
But the problem continues...
I have found many other users have faced this problem -- http://forum.xda-developers.com/showthread.php?t=1736118
I am disappointed. My phone is no longer in warranty... I am too late...
it is possible that using cyanogenmod and S2E (simple2ext) will work as a workaround until you send it to service center.
grab a copy of s2e and push it to /system/app/
Repartition your External-SD using the same method used for phones with low storage capacity, warning: it will erase all the data in it, so make backups
Start s2e and mark to move:
App and Private app
Applications data
Dalvik and download cache
This makes another partition, and it does not fix data, but at least you should be able to install apps.
I face this problem too. Please someone give us the solution.
Update: I flashed BAM Custom Kernel and put it in recovery mode. Attached it to the computer, but I'm stuck at this error message.
Thanks again.
More information
EDIT: There doesn't seem to be a /data partition at all! I feel I'm getting closer to fixing this.
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
alfrix said:
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
Click to expand...
Click to collapse
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
bruisedcrow said:
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
Click to expand...
Click to collapse
I think that the problem is when /tmp/updater.sh tries to mount /emmc your internal memory (EDIT: I've just noticed you tried with CM7, so, if I remember correctly, /emmc is the external memory, but I think that the problem is always the impossibility to mount the internal memory.) to backup your /efs directory. Because of the not avaible internal memory (/emmc) it simply exits and aborts the installation.
A simple change in updater.sh will allow you to install CyanogenMod, but wait for a confirmation from alfrix, maybe there's something more.
Anyway here there's a thread of a user with the same problem, he solved this by using the external SD as internal SD, as alfrix suggested.
strange, before touching anything try with the release i used that time (14.12.2011), if it doesn't work, then edit the updater.sh and remove
Code:
if ! /tmp/busybox mount -t ext4 /dev/block/mmcblk0p3 /data ; then
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3
fi
EDIT: is there any mmcblk on /dev/block?
Code:
ls /dev/block/
Weird the has mmcblk0 reappeared.
Code:
~ # ls /dev/block
ls /dev/block
bml0!c bml6 loop6 ram13 ram9 stl6 tfsr2
bml1 bml7 loop7 ram14 stl1 stl7 tfsr3
bml10 bml8 mmcblk0 ram15 stl10 stl8 tfsr4
bml11 bml9 mmcblk0p1 ram2 stl11 stl9 tfsr5
bml12 loop0 platform ram3 stl12 tfsr0!c tfsr6
bml13 loop1 ram0 ram4 stl13 tfsr1 tfsr7
bml2 loop2 ram1 ram5 stl2 tfsr10 tfsr8
bml3 loop3 ram10 ram6 stl3 tfsr11 tfsr9
bml4 loop4 ram11 ram7 stl4 tfsr12
bml5 loop5 ram12 ram8 stl5 tfsr13
So I tried
Code:
C:\Users\Bruised>adb shell
~ # /sbin/parted /dev/block/mmcblk0 mkfs ext2
/sbin/parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
/sbin/parted: invalid token: ext2
Yes/No? y
y
y
Partition number? 3
3
3
Error: Partition doesn't exist.
~ #
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
alfrix said:
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
What should I try next? 14.12.2011 download link is down.
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
alfrix said:
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
Click to expand...
Click to collapse
It installs it.
Code:
Checking state of RFS/EXT4...
Install from sdcard complete.
After I reboot CM9 boot screen loads then I get "Encryption unsuccessful" as shown here
After rebooting I get
Code:
CWM-based Recovery v5.5.0.4
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Formatting /cache...
Data wipe failed.
Heres the log file from the sdcard:
Code:
+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin
+ /tmp/busybox mount -t ext4 /dev/block/stl9 /system
+ /tmp/busybox mount -t ext4 /dev/block/stl10 /dbdata
+ /tmp/busybox mount -t ext4 /dev/block/stl11 /cache
+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/busybox umount -l /dbdata
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: Invalid argument
+ exit 0
First of all. I am biggest noob ever it is common problem but i did not find like mine. Because of phone low memory i installed int2ext and set 2gb size in cm10. But i figured out that is to much phone started to work a lot slower almost like on stock and flashed completly everyhing same again but partition is 1gb but then gapps started to fail ( gapps.andorid.com. process and 3,4 more things) and i just pressed ok ok ok. Then i restarted phone and again it couldnot connect to gsm network and those failures started to come out. Because of that i returned to recovery wiped clear dalvik installed new partition and then nothing phone is stuck at boot animation. I tried again and again and tried everything formating cache system data and then data dalvik tried all custom roms from original section and at the end. I copied backup i made before i installed first rom and restored it and now i when i turn on my phone i see HTC logo for a while then phone restarts and htc logo again and it moves me to recovery. I wiped that again but now when i select to install custom rom it stops during installation and says fail. I flashed phone more then 20x in past two days and i could not sort this problem and i dont have ideas. How to pass this problem and bring phone to life? ( i have to use old nokia s60 until i fix it so be quick . I know i did something wrong.
I think you are only wiping caches..
Do wipe/factory rest.
Wipe cache,
Wipe Dalvik cache in advanced
Format system and boot in mounts and storage..
Then flash your Rom..
If it still does nothing...
Follow NAND recovery by cute_Prince.. may be NAND burn..
Sent from my HTC Explorer A310e using xda app-developers app
What you can do is load into bootloader,click fastboot and connect your phone via usb.Flash a new recovery(try cwm) and then try flashing a new rom and recovering nand.
Thanks a lot on help. I reflashed boot again (connected to fastboot and recovery.bat) and when i now try to install new rom it stops and abort instalation at
Installing update : some symlinks failed
E:Error in /sdcard/cm-10....
(status 7)
Instalation aborted.
Please help
EDIT: I reed that this is common problem and i have fixed it by formating boot and system in mounts and storage. I can only install cm10.1 and mini cm. I cant install rom i have used before (cm10 b6). And now i get stuck and boot animation...
hey installed FLYROM v4....i havnt tried CM roms....what i did fr flashing FLYROM z i flashed yannou09z recoverry which z available on jaggyjaggs rooting tutorial....i use twrp nd other recveries....but wen i flash new rom it stuck on htc logo screen...so i flashed back to yannous....i then partitioned ma mmry card in ext4 through minitool wizard of 1 gb...then i wiped dalvich cache nd then i wipe data/factory reset thru recovery nd flashed flyrom...it wrks smoothly now....i recmnd yannous recovery fr pico....rest z uppon yu....
roshanjoseph23 said:
hey installed FLYROM v4....i havnt tried CM roms....what i did fr flashing FLYROM z i flashed yannou09z recoverry which z available on jaggyjaggs rooting tutorial....i use twrp nd other recveries....but wen i flash new rom it stuck on htc logo screen...so i flashed back to yannous....i then partitioned ma mmry card in ext4 through minitool wizard of 1 gb...then i wiped dalvich cache nd then i wipe data/factory reset thru recovery nd flashed flyrom...it wrks smoothly now....i recmnd yannous recovery fr pico....rest z uppon yu....
Click to expand...
Click to collapse
Tried to install flyrom rom. Installation was successful, but i get stuck at boot animation Any help i'm left out of ideas. And i changed recovery to TWRP (i been using cwm yanous90) and again same thing stuck at boot animation... Please help!
edit : And now in twrp when i try to install roms which i have installed above it shows again symlinks error ?!
If it helps
if you already have twrp recovery. try cute_prince nand recover method (flash_erase file) if not sure about nand burnt.
http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
and after that format/wipe every partition inclucing sdcard, when done then reboot in recovery and mount usb storage to pc and copy your desired rom( prefer cm9 or miniCM9) and flash it. wait for it to be succesful and next step is optional if you want sd-ext partition then reboot in recovery again and partition your card with ext3 and 0mb as swap space and wait for it to be succesful. if succesful then reboot to system.
Now i am 100% sure that it is burnt nand. I tried cute prince method have shell with # and when i copy paste command this is what happens... I copied flash_erase set to 775 and copied to xbin... In TWP i unmounted everything. When i type commands one by one su not found and then i cant cd to system/xbin... No i can see that i am close to solution. Please help i cant survive another week with nokia n97 mini...
adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
s./flash_erase -N /dev/mtd/mtd4 0 0
u
./flash_erase -N /dev/mtd/mtd5 0 0cd /system/x
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
~ # su
/sbin/sh: su: not found
~ # cd /system/xbin
/sbin/sh: cd: can't cd to /system/xbin
~ # ./flash_erase -N /dev/mtd/mtd2 0 0
/sbin/sh: ./flash_erase: not found
~ # ./flash_erase -N /dev/mtd/mtd4 0 0
/sbin/sh: ./flash_erase: not found
DJ_MY_SOUL said:
Now i am 100% sure that it is burnt nand. I tried cute prince method have shell with # and when i copy paste command this is what happens... I copied flash_erase set to 775 and copied to xbin... In TWP i unmounted everything. When i type commands one by one su not found and then i cant cd to system/xbin... No i can see that i am close to solution. Please help i cant survive another week with nokia n97 mini...
adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
s./flash_erase -N /dev/mtd/mtd4 0 0
u
./flash_erase -N /dev/mtd/mtd5 0 0cd /system/x
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
~ # su
/sbin/sh: su: not found
~ # cd /system/xbin
/sbin/sh: cd: can't cd to /system/xbin
~ # ./flash_erase -N /dev/mtd/mtd2 0 0
/sbin/sh: ./flash_erase: not found
~ # ./flash_erase -N /dev/mtd/mtd4 0 0
/sbin/sh: ./flash_erase: not found
Click to expand...
Click to collapse
If you are sure its a burnt nand, we have a thread here:
forum.xda-developers.com/showthread.php?t=2183130
And my phone is now running great! I installed cm10.1 after i flash_erase burnt nand. But because of symlinks error somewhere on xda i found that someone just added ./flash_erase -N /dev/mtd/mtd3 0 0 to cute prince method and thats it. And again my problem was that in recovery mount everything only sd card leave unmounted. And thats it Goodbye n97
Delete.
bootloop and recovery stuck
salil.bajaj said:
What you can do is load into bootloader,click fastboot and connect your phone via usb.Flash a new recovery(try cwm) and then try flashing a new rom and recovering nand.
Click to expand...
Click to collapse
Hi., my phone just got switched off for no reason and when i try to boot... stuck in boot animation... got to bootloader then recovery but recovery is stuck...i thought of flashing new recovery so i went to bootloader mode and connected the usb cable... it would rarely show FASTBOOT USB and pc would never recognize my device... I dont think i should go to Gaffar Market for this...
I am unable to install some roms(carbon and joilaroi rom) I think my nand is burnt
But i am able to instal cm10.2 by sarthak internal rom is showing 100 mb
ERROR -
Code:
symlink error
status7()
aborting installation
I have tried recovering nand by this method but didnt work from here- http://forum.xda-developers.com/showthread.php?t=2389445
it cleaned everything but there is still this error in flashing rom
right now i am using sense rom on Sd card
if u have any solution please tell
sakshamx said:
I am unable to install some roms(carbon and joilaroi rom) I think my nand is burnt
But i am able to instal cm10.2 by sarthak internal rom is showing 100 mb
ERROR -
Code:
symlink error
status7()
aborting installation
I have tried recovering nand by this method but didnt work from here- http://forum.xda-developers.com/showthread.php?t=2389445
it cleaned everything but there is still this error in flashing rom
right now i am using sense rom on Sd card
if u have any solution please tell
Click to expand...
Click to collapse
./flash_erase -N /dev/mtd/mtd3 0 0
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0
use all four of them
Saumitra Yadav said:
./flash_erase -N /dev/mtd/mtd3 0 0
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0
use all four of them
Click to expand...
Click to collapse
ok but in guide there was to format only these
Code:
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0
what is this mtd3 partition?
/system i think The guide you followed did not work for me So i erased the mtd3 partition also and it worked
Saumitra Yadav said:
/system i think The guide you followed did not work for me So i erased the mtd3 partition also and it worked
Click to expand...
Click to collapse
i am having some problem doing with recovery now can
can u provide the link of thread to erase from fastboot
i was unable to find
edit:thanks a lot it worked only system partition was burnt (in oc was mounted as rw:cyclops: )
sakshamx said:
i am having some problem doing with recovery now can
can u provide the link of thread to erase from fastboot
i was unable to find
edit:thanks a lot it worked only system partition was burnt (in oc was mounted as rw:cyclops: )
Click to expand...
Click to collapse
Why don't you change your recovery from terminal command?
su
cd sdcard
flash_image recovery recovery.img
Sent from my gt-1900 using xda premium
Taha Haq said:
Why don't you change your recovery from terminal command?
su
cd sdcard
flash_image recovery recovery.img
Sent from my gt-1900 using xda premium
Click to expand...
Click to collapse
read the post complete it worked afterwards:silly:
sakshamx said:
read the post complete it worked afterwards:silly:
Click to expand...
Click to collapse
Hi I am having a strange problem from last night.... I never use OC kernels coz m on class 4
but from yesterday night none of my memory scripts are working like m2sd or int2ext
Suddenly my rom is started saying insufficient memory while I have more than enough.... Is it nand burnt??
can u pls help me with this. If I dont use any memory script I am able to install apps....
cuteitsme said:
Hi I am having a strange problem from last night.... I never use OC kernels coz m on class 4
but from yesterday night none of my memory scripts are working like m2sd or int2ext
Suddenly my rom is started saying insufficient memory while I have more than enough.... Is it nand burnt??
can u pls help me with this. If I dont use any memory script I am able to install apps....
Click to expand...
Click to collapse
format ur partitions again(only partitions)
and flash a rom clean
sakshamx said:
format ur partitions again(only partitions)
and flash a rom clean
Click to expand...
Click to collapse
Yup that''s what i did...re partitioned and now everything seems ok.... Thanks dear....
Hello guys I've run into a weird problem.
I installed SlimLP alpha builds, everything was fine. One day, after trying to format /system etc. before flashing latest version, the tab started rebooting itself every 20 seconds. I tried to uninstall some apps, when I rebooted the tab the apps were back. I booted back into CWM recovery and when I tried to flash old version of this rom, it just stuck at the start. Moreover, when I try to exit recovery it always says "Root access probably lost. Fix?" But that does nothing.
I went into Odin and tried flashing two different stock roms, but it gave error "Complete(Write) operation failed" at system.img .It displayed my model number as "i9505" I then tried to flash through old Odin(v1.75) and it worked. But when I rebooted, it went back into SlimLP. I tried flashing TWRP and latest cwm version but it went back to previous version. The "download count" in Download Mode remained constant. I tried formatting /system and /data through cwm. There was no error but tab still boots straight into SlimLP.
I then tried my luck with ADB in cwm by trying to change file permission. With "chmod 755 /system" it gave the error "Read-only file system" With "mount" , it gave error "Operation not permitted". I booted into slimlp, quickly enabled root for "apps and ADB" through developer options and tried the commands but same error.
I also tried "NAND wipe all" in Odin, but it stuck at "Erase...." and then gave error after sometime.
Is there a way to completely wipe the OS now so I can flash stock one through Odin?
Which recovery version of cwm you have? Probably it will be lower than 6.0.4.4
It is 6.0.4.5
If you're tab still boots then try installing twrp using app called rashr
Tab reboots after 20 seconds, can't install app in that duration.
I9505 means you flashed the wrong firmware to your tablet, I 9505 is an international S4 phone rom.
You need a new tablet.
Reading is very important when it comes to flashing your Samsung devices.
Pp.
PanchoPlanet said:
I9505 means you flashed the wrong firmware to your tablet, I 9505 is an international S4 phone rom.
You need a new tablet.
Reading is very important when it comes to flashing your Samsung devices.
Pp.
Click to expand...
Click to collapse
I downloaded the correct firmware from sammobile, checked many times. Also, I flashed from other Odin version, which didin't display any model number. I just checked Odin3, and even without the device connected, it displays i9505 at top.
EDIT: Well downloaded Odin3 from another site, It didn't show any model number. Guess "i9505" was just a title edit.
I think there is a big in cwm, there are many having this problem with that recovery, all Android andi about it, try sending private message to him, our some other developer
Thanks, I'll try that and post it here.
Please do the following:
Boot/try to boot system
Try to get a dmesg using adb
Boot into recovery
Use adb to pull last_kmesg
Please get a recovery.log after wiping.
Attach the files here.
Send from OnePlus One using Tapatalk
Android-Andi said:
Please do the following:
Boot/try to boot system
Try to get a dmesg using adb
Boot into recovery
Use adb to pull last_kmesg
Please get a recovery.log after wiping.
Attach the files here.
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
I tried the commands like "adb shell dmesg > dmesg.txt" But got error "access is denied" Then I copied dmesg from console window, and pulled other files.
ssqw1 said:
I tried the commands like "adb shell dmesg > dmesg.txt" But got error "access is denied" Then I copied dmesg from console window, and pulled other files.
Click to expand...
Click to collapse
Can you upload the cwm you flash first and send me on pm?
Want to check if it's for our tab.
Will check your logs later.
Send from OnePlus One using Tapatalk
Did you used rommanager for cwm?
Send from OnePlus One using Tapatalk
Nope
Looks like a broken EMMC...
Please boot into recovery and use "adb shell":
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p9 /system
if it mounts without problems do the same for data
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p10 /data
Moutns without problem?
Please unmount now.
Code:
adb shell umount /system
adb shell umount /data
Let´s try to check the partitions now:
Code:
adb shell e2fsck -vf /dev/block/mmcblk0p9
adb shell e2fsck -vf /dev/block/mmcblk0p10
if you got error messages, please inform me.
Maybe we can reformat the partition by using adb shell.
Android-Andi said:
Looks like a broken EMMC...
Please boot into recovery and use "adb shell":
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p9 /system
if it mounts without problems do the same for data
Code:
adb shell mount -t ext4 /dev/block/mmcblk0p10 /data
Moutns without problem?
Please unmount now.
Code:
adb shell umount /system
adb shell umount /data
Let´s try to check the partitions now:
Code:
adb shell e2fsck -vf /dev/block/mmcblk0p9
adb shell e2fsck -vf /dev/block/mmcblk0p10
if you got error messages, please inform me.
Maybe we can reformat the partition by using adb shell.
Click to expand...
Click to collapse
It mounts without problem. Here are the results for checking:
First command:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell e2fsck -vf /dev
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
1699 inodes used (2.59%)
16 non-contiguous files (0.9%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1355
182363 blocks used (69.57%)
0 bad blocks
0 large files
1148 regular files
207 directories
0 character device files
0 block device files
0 fifos
0 links
335 symbolic links (335 fast symbolic links)
0 sockets
--------
1690 files
Second:
Code:
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p10: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>?
It doesn't proceed, tried typing Y, Yes and all other keys.
Can you give me the output from:
Code:
adb shell ls -l /dev/block
Please from recovery and booting rom.
Have you tried flashing stockrom + pit file to repartition?
Send from OnePlus One using Tapatalk
For reference http://forum.xda-developers.com/showthread.php?t=2627490
Send from OnePlus One using Tapatalk
Please give me mount output too.
Code:
adb shell mount
Sorry for the late reply, here are the files.
EDIT: I tried flashing the pit file with stock rom 2 times with Odin version 1.75, it flashed successfully but tab booted straight into SlimLP again.