Hey, on the Defy+, is it crucial to re-create the /tmp directory after wiping? I'm going off this link, which says that /tmp is symlnked and actually resides at /data/tmp, which means you have to re-create the directory. Otherwise, any attempt to flash something will result in this message
E:Can't make /tmp/update_binary
My question is, is this mandatory? I see lots of flashing tutorials, but nothing mentioning this /tmp directory hack. If you don't make it in adb shell, how do you do it?
.
Actually, I should clarify that i'm not too lazy to just try it.
My problem is I can't seem to get back to the initial recovery screen where I can choose to start adb daemon. But if I try to reboot system, I never get a blue LED to go into recovery; if from the CWM menu I try to restart recovery, I get taken to the screen with the knocked-out Android, from where I can only go to stock recovery.
Sent from my MB526 using xda app-developers app
Never mind. I stumbled on a couple posts warning to use Sndinit version 2 and to not flash stable, and that that would get me past the /tmp directory problem. That worked. But then I flashed Slimbean and lost my IMEI.
So I went back to square one, and then this time followed the instructions on the basic beginner's guide to flash the two-part sbf to root a BL7 stock rom. Then did Sndinit v.2, and now I'm back up with Slimbean.
Word of caution, if anyone's reading: I saw on that first boot of SB that I had my IMEI back, which I saw was restored going back to stock SBF. But then I changed the baseband for this region -- it was set to somewhere in Europe, and I'm in Southeast Asia. Then rebooted after that and saw my IMEI was missing again. I don't know why, but I rebooted again, and when it came back I had my IMEI. Strange.
Yes, this is a known bug.
Sent from my MB526 using xda app-developers app
Related
yesterday i rooted, and backuped my phone with clockwork. installed CM7 and it worked perfectly fine. i also restored my backup just to make sure i could go back. reinstalled CM7 once more and have been using it all day. today i decided i like all my default apps better on stock MT4G. so when i went to do the restore the process seems to work fine and i reboot the device to run my Stock image, but my phone wont go past the mytouch 4g splash screen. i can instally CM7 still and run it, but i want to go back to stock. Can someone help me figure out whats going on?
mumbo101 said:
yesterday i rooted, and backuped my phone with clockwork. installed CM7 and it worked perfectly fine. i also restored my backup just to make sure i could go back. reinstalled CM7 once more and have been using it all day. today i decided i like all my default apps better on stock MT4G. so when i went to do the restore the process seems to work fine and i reboot the device to run my Stock image, but my phone wont go past the mytouch 4g splash screen. i can instally CM7 still and run it, but i want to go back to stock. Can someone help me figure out whats going on?
Click to expand...
Click to collapse
You have to revert back to older Recovery 2.5.1.2 or you can install the new 3.0.0.6 as normal CWM won't able to handle it. This same issue has been covered many times. Read the quote below to better understand if you still have problem well then post back ill help.
jggimi said:
you are using the wrong version of Recovery to install the new kernel. I'm guessing #2, because it's very common for people to assume a higher number is better, and use CWM Recovery 3.0.0.5 with Froyo-based ROMs and hose things up really well.
Restoration options, if you are using CWM 3.0.0.5:
a) Restore from the Nandroid backup you made before overlaying your kernel. Oh, yeah, you can't, you didn't make one, otherwise you'd have already done that and wouldn't have posted....
b) Flash the appropriate CWM Recovery (2.5.1.2 for Froyo-based ROMs) using adb from your PC. Reboot into it, find the kernel you wanted to use, and reinstall it.
c) Install a Gingerbread-based ROM, such as CM7.
Pick a,b, or c. If you have any specific questions, please ask.
Click to expand...
Click to collapse
Just for preventive measures of a follow up question. I did the same thing you did, and when you try to flash CM7 again (because that is basically your only option) you might get stuck on the boot screen. In the recovery screen, go to advanced and clear your davlik cache before you flash it. Worked fine after that.
I don't know how to flash different recoveries. So I'm going to stick with cm7 till its updated.
Sent from my HTC Glacier using XDA App
mumbo101 said:
I don't know how to flash different recoveries. So I'm going to stick with cm7 till its updated.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Well use my old instructions on howto as you can manually flash it via terminal. Just put the 3.0.0.6 recovery.img in SDCard and flash it.
HKM said:
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
flash_image recovery /sdcard/recovery.img [hit enter]
Click to expand...
Click to collapse
You will need flash_recovery file along with 3.0.0.6.img for this meth to work so I provided you with everything as you just download it and unzip them in root of your /sdcard so you will have standalone flash_recovery and recovery.img in it.
Hi,
I have followed the tutorial given here.
With the only exception of this part:
On the computer, open terminal and run the following commands:
Code:
Code:
adb shell
su
cp -R /sdcard/bootmenu /data/bootmenu
For some reason the bootmenu directory was not present in the sdcard directory, so I created the directory myself and pushed the files for the bootloader 1 at a time (individually).
Everything goes well, until, after the installation, I reboot the phone. It stays on the Google logo. I have tried with and without the Google-Apps pack, but the result is still the same.
To get the phone back on track, I use the sbf file presented in this tutorial, but, although the phone does boot, nothing in it works. I tried flashing to other sbf files, but the phone then won't turn on.
Any idea on what is happening?
I have tried clearing the cache and factory settings, but to no avail as well.
I have also tried a nightly build, but this time it gets stuck on the Motorola logo... tired clearing cache and factory settings... no use.
Any information on this would be appreciated
Thanks.
Which sbf did you use?
Just install 2nd init for defy. It's much easier.
Sent from my MB526 using XDA App
I tried a lot of methods, none of which did not work. At the moment I am either installing the CM mod and getting my phone stuck at the logo page, or else, I am usin an SBF and the phone is simply not turning on.
The main problem I think that I installed full SBF's so downgrading the phone seems to be not possible. Is there some way in which I can get my Defy back to it's stock OS?
I followed the guide here. With that I managed to get a stable OS. I then was able to follow the guide on the Cyanogen website and install Cyanogen 7.
so you installed "leaked" gingerbread on your phone?
It's not easy to downgrade to froyo but i think it is not necessary, bacause it's a good starter platform.
If you did:
install shadow_2.3.4-134_DFP-10.sbf via rsd lite.
root with root4defy134.zip( install from stock recovery)
Install 2ndinit 2.0
After that there are 2 routes: install zipped rom(like WajkIUI_multilang_1.12.16_ICS.zip)
or
Restore rom from a nandroid backup( like MS2Ginger2.1-Defy.zip)
You will find tutorials on XDA.
So I downloaded new kernels and CM10 for my newly rooted N4. I did a backup before flashing the kernel and didn't pay attention to the error message saying cache was not found or whatever. But the kernel flashed fine and it booted up, nothing out of the whack. When I went back to flash CM10 it said the MD5 sum didn't match so the flashing processes didn't finish. Since my backup was ****ed up and the MD5 didn't match I couldn't restore the system either. Device will boot and will go into fastboot and recovery. Currently using CWM. If I turn on the device normally it will stay on the GOOGLE screen and it will not go into the boot screen. What do?
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
El Daddy said:
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
Click to expand...
Click to collapse
The CM10 zip itself is bad. How can I get another one on the phone? Or can I flash the CM zip without the file being on the phone? Thanks
Also, the error message popped up when flashing the CM zip was set_perm: some changes failed
E: Error in /sdcard/0/cmblahblahc zip
(status 7)
installation aborted
Should I turn off the signature verification anyway?
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
El Daddy said:
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
3 years of rooting and flashing stuff on 3 of my previous phones, there wasn't a time when I had to do this, or had to ask for help. Damn it.
Could you be a little more detailed in how do I go about doing so? As you can see my post count I am a bit of a noob Despite those 3 years. I just don't wanna mess up again, you know?
Thanks for everything dude
What screen should my phone be on? Just type that into the command prompt and it should work?
_thunderchild_ said:
What screen should my phone be on? Just type that into the command prompt and it should work?
Click to expand...
Click to collapse
Sorry I was out and about the past few hours.
You want to be in recovery. Custom recoveries allow you to use adb.
Rename the ROM something easy like CMrom.zip
Then put the CMrom.zip in the same location as adb on your computer.
Open the command window from that directory. (hold shift and right click; then choose open command window here)
Type the command: adb push CMrom.zip /sdcard/
It will push the file to the root of /sdcard/
Then you can flash it.
If that fails, use toolkit to download factory image and flash it through fastboot.
Oh man you guys saved my life. I cannot thank you guys enough. You won't believe how happy I was when I saw the bootscreen. Glad that was dealt with. Again thanks guys
Hey everyone I don't know if this is the right place to be posting this but I had the same problem as OP a few hours ago. I flashed LiquidROM and it got stuck on a boot loop. Needless to say, I panicked and used the adb push method since I decided to delete my AOKP ROM from my folder. Anyway, while panicking what I did was is before flashing, I backed up my entire SD card onto my laptop as ADB backup wasn't working and I pushed the entire folder using "adb push sdcard /sdcard/. Next thing I'm in recovery (CWM) and when I go through the flash from sdcard option, usually there were 3 options name 0/ and 2 others, however since I pushed the sdcard folder to /sdcard/ I get a 0/ at the top of the list which is where I would usually go but then underneath that I get all the folders I pushed! Is there any way to sort this out? I could attach pictures at some point for those of you who find it hard to picture what I'm describing Thanks in advance for any help!
Edit: just to add a couple of other things, my NANdroid had a checksum error so I cannot revert to stock without having to manually flash it which I cannot do at the moment due to a lack of WiFi, is there any way to sort this out? And the other thing was that for some reason sdcard cannot be unmounted at all in cwm, is it meant to be like that or am I missing something? Afaik its supposed to toggle.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
I want to revert everything but unlock. ROM root recovery the works. Can if be done? Thanks!
Sent from my Desire HD using Tapatalk 2
???
Sent from my HTC One V using Tapatalk 2
No. You need a computer to do it.
Sent from my Nexus 4 using Tapatalk 2
Can I unroot at least?
Sent from my Desire HD using Tapatalk 2
unroot is easy.
find under /system/xbin/su and remove it and also remove supersu.apk via the normal front end.
How about removing recovery?
Sent from my HTC One V using Tapatalk 2
Does anyone have a as stock ROM seeing as I'm on cm10.1 nkghtlies
Sent from my Nexus 7 using Tapatalk 2
cammykool said:
How about removing recovery?
Sent from my HTC One V using Tapatalk 2
Click to expand...
Click to collapse
You cant do it from tablet itself. You need a computer to do it em all. If you do not have access to a personal computer, let a friend do it and use their PC and do it yourself.
Sent from my Nexus 4 using Tapatalk 2
My USB port is broken. Computers don't recognise it
Sent from my Desire HD using Tapatalk 2
scream4cheese said:
You cant do it from tablet itself. You need a computer to do it em all. If you do not have access to a personal computer, let a friend do it and use their PC and do it yourself.
Click to expand...
Click to collapse
100% wrong answer.
The recovery can be flashed with the recovery booted. That partition is only read once during the boot process - it is no longer in use once the boot has completed (everything is running out of RAM). Same thing for the boot partition. So long as the ROM is rooted, you can flash either from the running OS, too.
The only thing the OP cannot do is relock the bootloader. But he has been told all of this multiple times now - this is something like his 3rd thread on the same topic.
cheers
And my last. I just need this done
Sent from my Desire HD using Tapatalk 2
Sounds like you are looking for a spoon-feeding.
I mean, how hard is it to locate a flashable Stock ROM over in the Dev forum?
Same goes for stock recovery images - just download them from Google.
http://lmgtfy.com/?q=Google+Nexus+factory+images
all they are are upgrade images.... not the full os to go from CM
okay maybe not.. but okay how will i flash the stock recovery?
You could try to backdoor a nandroid restore operation by manually creating a "fake" nandroid backup folder (containing only the recovery.img file and md5 files) alongside your other Nandroid backups. Think of this as doing a nandroid restore where the only component present in the backup is the recovery image.
I don't think you would want to try and hand-create a blob-style CWM backup, but I thought that CWM honors old-style backups if they exist alongside the blob backups (in the correct format). TWRP might be easier because it uses old-style (not blob-style) backups.
The touch version of TWRP allows you to restore individual components of a nandroid backup - for instance the recovery image only.
OK, that's one way, how about another? Use the "dd" command to flash the recovery image - either from a touch-interface recovery, or from a "rooted but unrooted" ROM.
What I mean by that is that from a root-shell command prompt, you can unroot the ROM by hand/command line... even though that terminal session still has root privileges. But don't exit that terminal session before you flash the stock recovery, because that will be the last opportunity to use root with the ROM booted!
for example (flash Stock rooted ROM first, the usual/normal way, download a terminal emulator app, verify that it can get root with "su" command, and then)
Code:
$ su
# mount -t ext4 -o remount,rw /system
# rm -f /system/xbin/su /system/bin/su /system/app/SuperSU.apk /system/app/Superuser.apk
# sync
# mount -t ext4 -o remount,ro /system
# dd bs=4096 if=/sdcard/stock-recovery.img of=/dev/block/mmcblk0p1
Reboot into stock recovery and perform a factory reset.
You can also do the very same set of instructions from touch-version TWRP's command line interface (preceding everything above with a "mount /system" command)
One last thing. Think about the above sequences carefully. For one, you should verify the MD5 signature of the recovery image of the copies(s) you transfer to the tablet is identical tho the MD5 of the copy you extracted from the Google factory image set.
Since you will be giving up root in the ROM (w/ the "rm" command), the only other privilege that will remain is via a custom recovery. If you blow that last step so that the stock rcovery won't boot, the ROM will still boot but you will have no way to perform a final factory reset.
Once you have unrooted the ROM, and flashed the stock recovery, there will be no path back to root for your device (never say never though, kernel exploits might appear).
good luck and take your time with this.
If you are jumping through all these hoops to get a USB connector repaired, I'm not sure why you are going to the trouble - flashing ROMs are wholly unrelated to physical damage to a USB connector. If you thought Google/Asus were going to repair the connector under warranty, it would be chicken-$hit for them to say "we won't repair a connector because you've been flashing". In any event, there's nothing to be done about your unlocked boot loader status, and that's going to be plain as day.
Want a log of the email? Lol. This experience has left a bad taste in my mouth with nexus devices
Sent from my HTC One V using Tapatalk 2
Guys, i made a noob mistake... Again
I was using "Antek Explorer XS" and set my root -> system partition to RW. I changed rights and suddenly my whole android crashed and android recievers stopped working.
Now the phone goes into Custom recovery because it fails to boot.
Fixing permissions in TWRP does not work.
I don't know what i did, but because of my root and ME changing stuff my android is broken. Is there a way to revert this by for example only flashing the system.img? Or do i have to reflash my stock android?
I had a NANDROID made, but i lost this one when i decided to backup only data instead. It now is nowhere to be found.
Rooted Nexus 4 on android 4.3 JWR66Y
Try just flashing system.img first. If it doesn't work flash factory image!
Sent from my Nexus 4 using xda app-developers app
Thanks, im a complete noob. Will i lose data or specific settings when flashing system.img and is there need to wipe specific caches?
My bootloader is still unlocked.
If i do lose data i will try to backup some, just in case.
If i have to reflash the whole image, will this cause data loss too (my main concern are apps)?
I found back my NANDROID backup, is it wiser to restore that one instead of flashing a factory image?
This all is new to me and i hate data loss. Detailed info is very much appreciated.
EDIT: Flashing system.img solved my problem. Thanks for the advice (again).
Again i learned a lot today.. Also how to use manual flashing instead of a toolkit + finding out that in some cases it's far more trustworthy and stable then a one click toolkit.
For everybody who makes the same uber dumb mistake as i did... Here some detailed explanation.
Flashing system.img will NOT cause data loss. Couldn't find an answer on that anywhere.
Today i also found out using a toolkit isn't always helpfull. I tried a sdcard pull but because the toolkit rebooted my phone it messed up. When just using command prompt and the "adb pull \sdcard/Destination folder\Destination file" command it pulled just fine.
Moments after the pull and having flashed the system.img (reboot into bootloader use command prompt to command "fastboot flash system C:/Destination folder/system.img") i got my phone back.. With all data intact!
DecypherT said:
Thanks, im a complete noob. Will i lose data or specific settings when flashing system.img and is there need to wipe specific caches?
My bootloader is still unlocked.
If i do lose data i will try to backup some, just in case.
If i have to reflash the whole image, will this cause data loss too (my main concern are apps)?
I found back my NANDROID backup, is it wiser to restore that one instead of flashing a factory image?
This all is new to me and i hate data loss. Detailed info is very much appreciated.
EDIT: Flashing system.img solved my problem. Thanks for the advice (again).
Again i learned a lot today.. Also how to use manual flashing instead of a toolkit + finding out that in some cases it's far more trustworthy and stable then a one click toolkit.
For everybody who makes the same uber dumb mistake as i did... Here some detailed explanation.
Flashing system.img will NOT cause data loss. Couldn't find an answer on that anywhere.
Today i also found out using a toolkit isn't always helpfull. I tried a sdcard pull but because the toolkit rebooted my phone it messed up. When just using command prompt and the "adb pull \sdcard/Destination folder\Destination file" command it pulled just fine.
Moments after the pull and having flashed the system.img (reboot into bootloader use command prompt to command "fastboot flash system C:/Destination folder/system.img") i got my phone back.. With all data intact!
Click to expand...
Click to collapse
Good to hear that! Enjoy your N4!
Sent from my Nexus 4 using xda app-developers app
Yeah just for your reference.
All your downloaded apps, data and sdcard is stored on the data partition.
Apps = /data/app/
Data = /data/data/
Sdcard = /data/media/
Sent from my Nexus 4 using xda app-developers app
Well this is a bit late, but you could have fixed the problem using chmod in adb shell and set the folder permission back to 755.
xda app
@Alex240188, Thanks!
@eksasol, better late then sorry. Would be good to know earlier. But still good if somebody makes the same mistake and finds this thread.
Send from my Nexus 4