Related
Hi there...
I'm finally considering rooting, however all the guides lead to flashing a custom rom... but actually I don't want to flash a custom ROM, I want to keep everything as it is, with the difference that I (and preferably only I) can become super user on the shell when I need to do some changes (like fixing the stock widget bug in the internal database).
I've read this right now:
http://forum.xda-developers.com/showthread.php?t=724741
And they say I can flash this files called EngTools.zip
Does this also work on the Hero assuming the guide (PossibleGSMRoot or something... fromt he villainforum) works on my phone?
I don't even want to permanently have some kind of AmonRa blabla recovery boot image on my phone. If I need it while I get root that's fine, but I want to get rid of it afterwards. I really don't need root for any applications liek overclocking etc. etc. just for smaller dives into the files system and changes there via adb.
olafos said:
Hi there...
I'm finally considering rooting, however all the guides lead to flashing a custom rom... but actually I don't want to flash a custom ROM, I want to keep everything as it is, with the difference that I (and preferably only I) can become super user on the shell when I need to do some changes (like fixing the stock widget bug in the internal database).
I've read this right now:
http://forum.xda-developers.com/showthread.php?t=724741
And they say I can flash this files called EngTools.zip
Does this also work on the Hero assuming the guide (PossibleGSMRoot or something... fromt he villainforum) works on my phone?
I don't even want to permanently have some kind of AmonRa blabla recovery boot image on my phone. If I need it while I get root that's fine, but I want to get rid of it afterwards. I really don't need root for any applications liek overclocking etc. etc. just for smaller dives into the files system and changes there via adb.
Click to expand...
Click to collapse
Hmmm. If you are on 2.1, then you can use the GSM root i posted over at VR. The recovery needs to be flashed to the phone though, so you can flash zips to the phone from there.
As for your wish to get rid of the patched recovery afterwards, you're missing out a lot, but if you can find the stock recovery img file, you can simply flash that using
"flash_image recovery FilenameHero.img" via the phone's shell or adb (once rooted, presuming you added the flash_image binary).
As for that file, I don't know, as I've never checked if that will work on the hero.
I'd be inclined to say DON'T TRY IT, since it will contain a kernel, and flashing the wrong kernel can brick your device's radio, essentially ruining it.
But if you locate the correct files for the GSM hero, and package them similarly, you could flash that onto your phone via recovery
Bear in mind the stock HTC ROM is basically full on the system partition, so you might have issues actually fitting the files on.
I've been a lurker for some time here but just before I had thought about exactly the same issue as OP... I always wondered why there's no way to just get root access temporarily. Most people told me I'd have to flash a custom ROM.
So today I finally looked into the matter and based on your (anon2122) post on VillainROM and the Eris exploits etc. I managed to do exactly what I wanted... and thought it's time to get an account...
I only really needed root for the Stock app currency issue: [HTTP]://forum[DOT]xda-developers[DOT]com/showthread[DOT]php?t=719149 which I was now able to fix.
HTC Hero GSM soft root guide by ixampl
(... credits belong to / based on: [HTTP]://www[DOT]villainrom[DOT]co[DOT] uk/viewtopic[DOT]php?f=110&t=2096)
1 Flashing a custom recovery image
1.1 Backup (1)
Code:
adb shell mkdir /data/local/backup
adb shell cat /data/local/rights/mid.txt > /data/local/backup/mid.txt
1.2 Uploading custom recovery image and image flashing tool and setting correct permissions
Code:
adb push recovery-RA-hero-v1.6.2.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-RA-hero-v1.6.2.img
adb shell chmod 777 /data/local/flash_image
1.3 Center piece of the permissions exploit for the recovery ROM
Code:
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
1.4 Normal reboot
Code:
adb reboot
1.5 Now that the recovery ROM (/dev/mtd/mtd1) is accessible: Backup (2)
Code:
adb shell cat /dev/mtd/mtd1 > /data/local/backup/recovery.img
1.6 Flashing the previously uploaded custom recovery image
Code:
adb shell /data/local/flash_image recovery /data/local/recovery.img
1.7 Rebooting into recovery mode
Code:
adb reboot recovery
2 Adding root shell (optional)
2.1 Mounting all devices
Code:
adb shell mount -a
2.2 Adding rootsh
Code:
adb shell cat /system/bin/sh > /system/bin/rootsh
adb shell chmod 4755 /system/bin/rootsh
2.3 Rebooting into system
Code:
adb reboot
After this you can flash the recovery.img you backed up in step 1.5 just as you flashed in step 1.6 (adjust the parameters accordingly).
ixampl said:
I've been a lurker for some time here but just before I had thought about exactly the same issue as OP... I always wondered why there's no way to just get root access temporarily. Most people told me I'd have to flash a custom ROM.
So today I finally looked into the matter and based on your (anon2122) post on VillainROM and the Eris exploits etc. I managed to do exactly what I wanted... and thought it's time to get an account...
I only really needed root for the Stock app currency issue: [HTTP]://forum[DOT]xda-developers[DOT]com/showthread[DOT]php?t=719149 which I was now able to fix.
HTC Hero GSM soft root guide by ixampl
(... credits belong to / based on: [HTTP]://www[DOT]villainrom[DOT]co[DOT] uk/viewtopic[DOT]php?f=110&t=2096)
1 Flashing a custom recovery image
1.1 Backup (1)
Code:
adb shell mkdir /data/local/backup
adb shell cat /data/local/rights/mid.txt > /data/local/backup/mid.txt
1.2 Uploading custom recovery image and image flashing tool and setting correct permissions
Code:
adb push recovery-RA-hero-v1.6.2.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-RA-hero-v1.6.2.img
adb shell chmod 777 /data/local/flash_image
1.3 Center piece of the permissions exploit for the recovery ROM
Code:
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
1.4 Normal reboot
Code:
adb reboot
1.5 Now that the recovery ROM (/dev/mtd/mtd1) is accessible: Backup (2)
Code:
adb shell cat /dev/mtd/mtd1 > /data/local/backup/recovery.img
1.6 Flashing the previously uploaded custom recovery image
Code:
adb shell /data/local/flash_image recovery /data/local/recovery.img
1.7 Rebooting into recovery mode
Code:
adb reboot recovery
2 Adding root shell (optional)
2.1 Mounting all devices
Code:
adb shell mount -a
2.2 Adding rootsh
Code:
adb shell cat /system/bin/sh > /system/bin/rootsh
adb shell chmod 4755 /system/bin/rootsh
2.3 Rebooting into system
Code:
adb reboot
After this you can flash the recovery.img you backed up in step 1.5 just as you flashed in step 1.6 (adjust the parameters accordingly).
Click to expand...
Click to collapse
That is a nice method.
I've long thought about making something similar, so maybe today I'll try, as an idea has come back to me...
I am thinking that I can avoid the whole recovery flashing, though I'm not going to say the idea till I've thought it through, as someone might try it before I realise how stupid an idea it is...
But I'll certainly see if it can get permanent root sorted out on the phone, although it won't give root adb access, as that is defined in the boot.img, though I guess I could flash that while I'm at it...
Good work.
Thanks!
Yes, a method to (safely) acquire super user access without flashing anything would be highly appreciated There's a small risk involved with flashing. Granted it usually causes no issues, but there is the slight possibility of bricking your phone.
Good work.
Click to expand...
Click to collapse
Thanks, although - as you know - I really didn't do anything special there
[...] although it won't give root adb access [...]
Click to expand...
Click to collapse
Yes, that's a minor annoyance, but really minor ... for the currency fix I naturally couldn't do
Code:
adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
or
Code:
adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
but it's not that hard to just work around that via /data/local:
Code:
adb shell
$ rootsh
# cat /data/data/com.htc.dcs.service.stock/databases/stock.db > data/local/stock.db
then pull from there etc.
I really think "rooting" is a misnomer for most of the current guides.
I can see that most people "root" their phone in order to get custom ROMs (and I have no issue with that, it's just too much overkill for someone who just wanted to fix a small bug ) but In fact most people don't care about rooting per se, they care about flashing a recovery image which enables them to flash custom ROMs.
I actually wanted to try:
Code:
adb shell ln -s /dev/mtd/mtd3 /data/local/rights/mid.txt
...and see what happens if I remount after boot. If it causes the system to follow back the link with user permissions for the recovery ROM, maybe the system ROM could be (write-)accessed as well. Then again, it was my first venture into rooting so naturally there would have been no way to fix a broken system image safe for reflashing the 1.5 RUU.
Do you have any details about what the original purpose of the (original) mid.txt was? I mean, it was there, sitting in a directory named rights... quite an invitation (of course, we didn't actually "set" rights in that file or anything for the exploit, but still...)
Is it safe to delete mid.txt and will it be recreated with some default values by the system?
Click to expand...
Click to collapse
New as of Saturday August 8th
I will update the files every time I find a problem
WARNING PLEASE READ:
Project JIT is highly highly experimental! If you are to do this, MAKE A NANDROID BACKUP IN ROM MANAGER OR RECOVERY! There are always chances of something going wrong. I nor anyone else is responsible of what happens.
Experienced users please know the possible risks:
Boot Looping, requiring a restore
Constant FC's
Wiping everything
These are just the risks, please note it is not 100%
JIT stands for Just in time compiler. It does not like Touchwiz, so download ADW.Launcher or LauncherPro before starting and set it as default.
This whole process is in ADB. If you dont know how, or what it is, DONT DO IT!
Things to do before you start:
-Download a different launcher than TouchWiz
-Make a backup in recovery or Rom Manager
-Did I mention DO A BACKUP!
-If you have an external SD card, pull it out
-Download the vmlibs file
What I expect you to know before you start:
-ADB
-What JIT is
-How this will effect the performance
-The risks
-How its not my fault if you screw your phone over
-How experimental this is
-How to make a nandroid backup
-How to make a nandroid restore
Remember, this is experimental and I cannot guarantee for it to completely work.
Download This- vmlibs.zip
Then follow these steps:
-Make a backup!!!
-Create 2 folders on your internal sdcard: “jit” & “dalbk”
-Extract the vmlibs.zip to the “jit” folder on your sdcard
-Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad, text edit or similiar program.
-Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Edit the following line:dalvik.vm.startheapsize=8m
to: dalvik.vm.startheapsize=12m
-Save the changes
-Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit, but if your phone boot loops, thats why you have A BACKUP!
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
While in recovery, wipe the dalvik cache, this will prevent it from boot looping.
To Disable
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
If that fails, that is why you have a backup. To restore, go to recovery, click on nandroid, and restore from your backup.
Reserved for future posting
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
LGSilva said:
Will this work with the sd card cache hack?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It didn't here. Not sure if that is due to other fsckup or the fact that I was running I9k rom with my kernel and sdcard hack...
Restoring to stock to give this a whirl
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
hansmrtn said:
tommarow I will update the vmlibs file and see if it works better.
Oh, and tell me what your problems are
Click to expand...
Click to collapse
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
NukaCola said:
Doesn't boot past the white at&t screen. Again, I was running I9k rom with custom kernel and ext hack, not exactly the cleanest test bed. Flashing stock to test now (can't get into recovery on this thing anyway it seems).
Click to expand...
Click to collapse
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
hansmrtn said:
Hold on. Before you do that, let me up the file.
EDIT:
Here is the updated one, its in the first post too
It should work better. I used it just now, and it works for me
Click to expand...
Click to collapse
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
NukaCola said:
Too late
Same story with the stock rom and old file, just FYI. Flashing back and trying the new one.
Click to expand...
Click to collapse
Yeah, thats why I had to fix some stuff lol. I noticed that it wouldnt go past the att screen. Now it should work correctly. The worst that could happen now is it boot loops on the Galaxy S screen
Haha I was just about to post the same problem, downloading new file and trying it again!
Zilch25 said:
Haha I was just about to post the same problem, downloading new file and trying it again!
Click to expand...
Click to collapse
Hey, when you edit the build.prop to add the dalvik vm line, can you look for the vm heap size and change it from 48 to 32? I am about to test doing that, and I would like more feedback
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Zilch25 said:
Doh, didn't read this until after applying it all... it's in the process of booting though- it got past the AT&T logo so that's progress!
Click to expand...
Click to collapse
Dont worry, I will try it
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Zilch25 said:
ATM I'm now stuck sitting at the GalaxyS logo, I'm going to give it a little more time, but I suspect it might be stuck.
Click to expand...
Click to collapse
Do you know how to run a logcat?
Its gonna take a while because its re writing the dalvik cache
That I do not, but I'm willing to try it if you can give me a quick crash course
Zilch25 said:
That I do not, but I'm willing to try it if you can give me a quick crash course
Click to expand...
Click to collapse
Well I am looking at my logcat now, and it is just repeating boot animation.
A logcat is useful, so how you do it is adb logcat.
I changed a couple things to test around with here is what I did-
I added all of this to the build.prop-
#JIT
dalvik.vm.execution-mode=int:jit
and changed:
dalvik.vm.heapsize=48m
to
dalvik.vm.heapsize=32m
Right now I am resorting to try the older vmlibs with the new settings
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Zilch25 said:
Ran logcat, it's also trapped at looping animation, and I didn't touch the heapsize
W/BootAnimationSEC< 2194: ms4631 - Repeat Loop Animation
Over and over and over, is there something else in the buffer you'd like me to look for?
Click to expand...
Click to collapse
No thanks for the feedback. Its only worked for me once, and then when I rebooted it got stuck in a boot loop.
Whats a device thats running android 2.1, and has a jit hack that is extremely similar to the Galaxy S series?
Hi everyone,
A few days ago I got the OTA 2.2.1 on my MT3G and then rooted it using the SuperOneClick tool. I was able to remove all useless apps, pushed others to /system/app with Root Explorer, etc., there is only one to do, and I am clueless: how to replace the stock Android System Recovery <3e> with a custom recovery image, so I can do Nandroid backups, flash .zip files, etc?
I used the ROM Manager app to flash Clockwork, got an "Installation successful" confirmation, but then on reboot into recovery mode my phone got stuck on the MT3G logo. I had to remove the battery, then in second attempt the phone booted into the <3e> image. Restarted again, opened the ROM Manager, according to it Clockwork was installed. Total craziness! Then I tried to flash it using Better Terminal Emulator (su, flash_image recovery /sdcard/Clockwork.img) but I got a "flash_image: not found" message, though I had the image on my sd card.
Any good ideas, folks?
All useful suggestions much appreciated, thanks!
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
It's kinda relative to the topic. I'm stuck on clockworkmod and would like to get back to stock recovery as the new HBOOT doesn't let me flash roms. Is there any way I can do so?
Look in my guide... all the files, steps and binaries are included...
Check out my signature!
Thanks, Asadullah. One more question: Are there different versions of flash_image for different android versions, because I saw in another forum a user complaining he/she didn't use the right binary.
Edit: I've extracted a flash_image binary from CM 6, hope it will work
Edit2: It worked, thanks a lot, man!
I think that flash_image from different devices is different someone correct me if I'm wrong. Glad it worked
Sent from my HERO200 using XDA App
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
lgtsanev said:
I forgot to ask you one more question, don't want to open a new thread for this one, perhaps you can help again
I put the code you gave me through the terminal, since adb denied me of su permission. I installed the SDK, and after typing "adb devices" in cmd it saw the phone. "Adb shell" worked (saw the dollar sign), but then intead of getting the pound sign, su gave me "permission denied". But I get the permission when using the terminal. I also cannot see the phone directories when I open DroidExplorer, but otherwise it sees the phone and I get su permission when I use its command prompt. I thought there may be a problem with the root, but if there was, then how was I able to delete and push system apps and install the custom recovery? What do you think may cause the problem? Thanks.
Sent through XDA App
Click to expand...
Click to collapse
I know it's been a while and you didn't get a reply, and while I found this thread because I too am having enormous trouble rooting this whatever it is cheap chinese android 2.2.1 momo 2 thing covered completely in chinese language apps that I simply cannot use even for the low price it cost me - I thought I'd offer an answer, most likely wrong, but one that may help the next person who may fall into your position.
adb root is an option to start the adb service in root mode, and I can only assume that means for the device.
As I have not been able to get this thing sorted, not knowing what it is really - no phone, no camera, no buttons on the case apart from power/sleep - Home/Esc which do nothing on booting apart from alert the PC to detect a new USB device, no market access, but otherwise exactly what I required - I dont know if it'll help.
But I hate threads left in a question, because I always find them. And this circle of frustration seriously should not be real, it just cannot be this damn hard to do something...
yikes!
help please
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
sky rider said:
i cant get it how to use it.. i havve recovery & flash img
please if u dont mind can u please litel more explain it
thanks
Click to expand...
Click to collapse
root your phone
install terminal emulator on your phone
type in everything that you quoted except for adb shell
Confused in differences
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Jkhim said:
Sir, is there a differences behind these flash_image recovery and recovery.img because its too confusing to think that they are the same or not
Click to expand...
Click to collapse
Honestly it's been so long I forgot ?? I don't think you need too use flash image anymore
rm failed????
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sh: ./flash_image: not found how to fix this sir? im so new about this, sorry about that
---------- Post added at 05:22 AM ---------- Previous post was at 04:43 AM ----------
Asadullah said:
They've been excluding flash_image from htc roms lately. What your gonna have to do is put flash image on your sdcard with the recovery.img. Then mount your sdcard and run the flash_image from your sdcard and flash the recovery image. After your done then you remove the installrecovery.sh from system/etc. That is what keeps installing the factory recovery when you reboot. I get home and onto a decent internet connection in a few hours and I'll upload some adb commands to help you do this.
make sure you have the recovery.img and flash_image on your sdcard
run these commands in adb
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/mtdblock3 /system
rm /system/etc/install-recovery.sh
cd sdcard
mount -o remount,exec /dev/block//vold/179:1 /sdcard
./flash_image recovery /sdcard/recovery.img
exit
exit
Click to expand...
Click to collapse
sir is this CM.12 cyanogenmod fakelollipop is an example of flash_image even its in a zip file? because i cant get it at all, im stuck at flash_image not found
Note 3.16 and below are for HoneyComb bootloader 3.17 & up are for ICS patched bootloader.
This is built from my forked Amon Ra recovery source.
WARNING UNLESS YOU ARE VERY FAMILIAR AND COMFORTABLE USING COMMANDLINE/TERMINAL DO NOT MESS WITH THE EXT3|EXT4 MENU. MESSING WITH THE PARTITION FORMATS CAN LEAVE YOUR ICONIA IN A STATE THAT IS UNABLE TO BOOT NORMALLY AND REQUIRES FIXING VIA COMMANDLINE. Fix for ignoring this warning is done by running "iconia_repair.sh help" from command line in recovery.
Full source for both Apache licensed recovery and GPL licensed kernel & busybox are here
Recovery Features:
Special features for acer iconia :
Touch enabled UI
Can use usb flash drive or normal sdcard as sdcard to flash roms and to use in nandroid backup/restore.
Automatically runs itsmagic on boot
External sdcard mass storage works on iconia
Automatically backs up usb serial (uuid) and the start of mmcblk0 in nandroid backup.
Will not remove /data/media unless full ext wipe option is selected (off by default)
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup items with [X] to restore
Nand Restore Clockwork : browse to and restore cwm backup
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse.
Toggle Signature Verify : Toggle on/off signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all (data, cache, android_secure & dalvik if outside of /data)
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe system
Wipe sdcard
Wipe .android secure : Wipes froyo+ native .android_secure on sdcard
Toggle full ext wipe: Toggles full or quick wipe of ext partitions
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (
Mounts:
Gui mounts to avoid typing in terminal to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix Permissions
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check Battery Lvl
Ext3|4 menu: Formatting and re-formatting of partitions
Developer menu:
Make and flash boot from zImage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Trouble Shooting:
Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log which will be on your external sdcard. It should have detailed cause of error if its not self-explainatory upload it here as an attachment and then post details about the error. Posts without the log are a complete waste of my time and will be ignored as there is no usable info to assist me in troubleshooting it. You will also be told to go visit /dev/null.
Special Thanks:
Thanks to :
Amon Ra
Koush
Sc2k for itsmagic and getuid.ko
Gweedo767 & CEnnis91 for the touch ui
Skrilax_CZ for patched ICS bootloader & setbootmode
Download Section:
To flash on HC bootloader(requires root):
run itsmagic then
Code:
adb push recovery-ra-iconia-3.13-gnm.img /sdcard
adb shell
su
dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
To flash on ICS Patched Bootloader:
fastboot flash recovery nameofrecovery.img
V3.17 Recovery flashable zip : recovery-ra-iconia-3.17-gnm.zip
ICS recovery-ra-iconia-3.17-gnm.img
md5sum e74dd63395baed6d00c724024ab2d5cc recovery-ra-iconia-3.17-gnm.img
recovery-ra-iconia-3.16-gnm.img
md5sum 357a7033171585005db89d505b6b7c65 recovery-ra-iconia-3.16-gnm.img
recovery-ra-iconia-3.15-gnm.img
md5sum f40fc8fe8708df75583338d09be33ea0 recovery-ra-iconia-3.15-gnm.img
recovery-ra-iconia-3.14-gnm.img
md5sum d69390b62dd914a440ca2ae90ff95a0a recovery-ra-iconia-3.14-gnm.img
recovery-ra-iconia-3.13-gnm.img
md5sum 292d0a37cc7971baab2b32d6dae0d74c recovery-ra-iconia-3.13-gnm.img
Flashable zip for 3.13 is here http://forum.xda-developers.com/showpost.php?p=21727826&postcount=13
Changelog 3.14 :
Added menu option to wipe flexrom and also included it in the default wipe all
Added option to flash a zip from internal storage
Added warnings on using the ext3|4 menu
Added recovery shell script called iconia_repair.sh for users that ignore the above warning and have corrupted their partitions. To use call "iconia_repair.sh help" from adb shell in recovery.
Changelog 3.15
Fixed wipe boot option on emmc devices
Fixed ext3|ext4 format menu for iconia & updated the iconia_repair.sh script to match (still may error 1st time if users used this option on 3.13 or 3.14 to format use script to repair and it will work properly from there out)
Itsmagic is now built into recovery binary
Sdcard is now unmounted after flashing a zip from it.
Changelog 3.16
Fixed nandroid restore from usb stick
Added ability to nandroid restore a cwm backup from usb stick
Changelog 3.17
Updated for ICS patched bootloader
Removed auto run of itsmagic (still there from cmd line)
Updated Mass storage in recovery to 2.6.39 kernel
Compiled setbootmode into recovery -- call setbootmode from cmd line to use
Default quick wipe and nandroid backup skips /data/linux directory if present -- toggling full ext wipe will still remove and reformat 100% of /data
Note: nandroid backup folder is changed from nvmem=* to your devices serial # so you may need to manually move old RA backups into new folder.
Updated su & superuser.apk to current
Seems cool ill try it out in am.
Sent from my HTC Inspire 4G using Tapatalk
Thanks bro. Just downloaded it. Will give it a try in the am. Off to bed!
Just gave it a quick test. Seemed to work fine (touch controls & backup). Haven't tried a restore yet, which is the true test.
Much thanks! This looks extremely promising.
just curious, being a first time venturing a little bit with my a500, how does one run "itsmagic"? i'm having issues with my windows 7 x64 pc recognizing my tablet running thor's latest ICS build 89 over adb, so would it be possible for somebody to make this as a flashable zip from the recovery i already have installed? or is that crazy... i flash new recoveries all the time for my fascinate or droid 1 in CWMR so I'm just curious. thanks!
Same here ive looked at the old its magic thread from way back and still not sure how to call it.
would some one be able to put together s CWM .zip for us to save alot of the same posts?
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1665 KB/s (5001216 bytes in 2.932s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ # sync
sync
[email protected]:/ # sudo
sudo
sh: sudo: not found
127|[email protected]:/ # su
su
[email protected]:/ # exit
exit
[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # itsmagic
itsmagic
sh: itsmagic: not found
127|[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1932 KB/s (5001216 bytes in 2.527s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ #
this is what i get. not a directory? Does thor's ICS have something set up differently? I'd love to get a legit recovery up in here. Thanks.
---------- Post added at 11:56 AM ---------- Previous post was at 11:43 AM ----------
just for anyone looking in, joe9002 for example, I followed the steps from here to find out you have to run the second set of command in the terminal on the tablet. much easier with a usb keyboard, i might add. got it installed and running nicely. it ain't pretty, but the touch does work. I guess i was expecting more like TWRP with big icons, but not having to use the way too recessed volume buttons is awesome. thanks guys!!!!!
please provide a flashable zip....lazy kid)
easy install
i have used acer recovery installer
http://forum.xda-developers.com/showthread.php?t=1226191
josinpaul said:
please provide a flashable zip....lazy kid)
Click to expand...
Click to collapse
+1, would someone please do a cwm flashable zip for this ?
Thank a million
Sent from my A500 using Tapatalk
If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.
I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE
erica_renee said:
If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.
Click to expand...
Click to collapse
NOT logical at all!
You need a script run to install it. See post above!!!!
kjy2010 said:
I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE
Click to expand...
Click to collapse
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?
internetpilot said:
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?
Click to expand...
Click to collapse
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Oops...see that now in the OP. Thanks. Sorry, the running itsmagic as part of the install process through me for a loop. I know that I've seen Thor's CWM recovery automatically loading it, and I was worried that with this recovery we'd have to do it manually.
Alright. Maybe I'll be the guinea pig and try a restore.
kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
internetpilot said:
Alright. Maybe I'll be the guinea pig and try a restore.
Click to expand...
Click to collapse
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.
drellisdee said:
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.
Click to expand...
Click to collapse
Thanks again dell! We needed an alternative to the GPL non-compliant CWM that we had!
Your work is GREATLY appreciated and the touch screen is an added bonus!
Very nice addition to the A500, thanks for the hard work.
Hi everyone,
my N7 (unlocked, stock, latest OTA, maybe was rooted) is not booting past the Google logo. I can access bootloader and recovery and through custom recoveries adb shell sbin/dmesg. also in stock adb sideload works. but when it is stuck in google logo it is detected as nexus 7 but I can't access it through adb (no devices listed).
What I did already:
stock recovery: factory reset
cwm recovery: wipe dalvik cache, fix permissions
reflashed factory image JZO54K and JOP40D
formatted /system and reflashed
fastboot oem lock & fastboot oem unlock: after this it will show the boot animation for ~7s and reboot
also i waited 20mins after flashing factory images - enough so it at least can show the boot animation
this is what fastboot currently shows:
FASTBOOT MODE
product name - grouper
variant - grouper
hw version - ER3
bootloader version - 4.13
baseband version - n/a
serial number - 015d2109f31c0415
signing - not defined yet
LOCK STATE - UNLOCKED
here are two dmesgs: http://pastebin.com/T8pexUa3 and http://pastebin.com/y2sXSC5n
and here's the video of a startup after fastboot oem lock + unlock: http://www.youtube.com/watch?v=Sj3E3Emkz2U
and here's a log of one flash: http://pastebin.com/z5Bue4jL where everything seems perfectly fine
Some more symptoms: non of openrecovery-twrp-{2.3.3.0, 2.4.0.0, 2.4.1.0}-grouper.img are properly booting (only splash screen is displayed) and when I try to do some tasks like mount /system with cwm 6.0.1.0 or factory reset with twrp 2.2.1 (part of galaxy nexus 7 toolkit) the recovery will freeze so I have to reboot. also cwm gets awfully slow after some tasks.
I am out of my wits, can anyone help? If you give me instructions I can provide more dmesgs.
hi aha27,
Sorry about your problem. You are to be commended though, for the preparation and detail you provided in describing your situation - too bad most are not that thorough.
That video is an unusual bootloop. With "normal" bootloops the kernel stays up and the android layer cycles endlessly in it's startup checks - but your video looks much more like a kernel panic occurs, as the screen goes back to a bootloader display.
I looked briefly through one of your dmesg boot logs, and didn't spot anything unusual. The facts that:
(a) you can successfully re-flash stock roms, including file system re-creation
(b) you can run adb shell commands interactively
is evidence that the kernel has no difficulty booting and that perhaps the flash filesystems are all OK too.
What sticks out is your report that the recoveries also do not proceed completely to show their touchscreen interfaces.
Here is something to try
(1) perform soft-boots of the recovery with fastboot, for example:
fastboot boot openrecovery-twrp-2.3.3.0-grouper.img
As this requires no writing nor reading of the eMMC Flash memory, if it fails to setup the display correctly, perhaps you have a hardware problem that is unrelated to flash memory. (As you tried multiple recoveries, you may have already done this - it wasn't evident whether you flashed your different recoveries or soft-booted them)
Note also that you can run several adb sessions simultaneously, so in separate windows with the recovery running you can certainly be doing
C:\fubar> adb shell logcat > logcat_output.txt
and
C:\fubar> adb shell cat /proc/kmsg > kernel_log_output.txt
[ If you are using cygwin or linux you can spice this up a little, e.g.
$ adb shell logcat 2>&1 | tee logcat_output.txt
$ adb shell cat /proc/kmsg 2>&1 | tee kernel_log_output.txt
... as both of these block waiting for more output, in the latter case you get to see things happening in real time as well as capturing the output for later analysis ]
(2) see if anything is leftover in /proc/last_kmsg on the boot cycle immediately following the "bootloop". It might be possible to jump the device into fastboot mode by pressing Vol-Down the moment the Google logo first reappears. From there, soft-boot a recovery and capture the output of
adb shell cat /proc/last_kmsg
(3) Start your adb server on the PC and launch the "bootloop" and see if you can get a shell before the crash occurs. If you can get one before the crash occurs maybe you will be lucky enough to catch a problem via
adb shell cat /proc/kmsg
or
adb logcat -v threadtime
Note that if you have installed a fresh ROM, you can toggle ADB debugging on by mounting /data and
# mkdir /data/property
# chmod 700 /data/property
# echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
# chmod 600 /data/property/persist.sys.usb.config
(4) I also noted your comment about "freezing if I mount /system". Note that when you flash the factory image, /data and /cache are handled differently than /system, even though all 3 are ext4 filesystems. For the first two, the process is "erase, mkfs, write", whereas for /system all you get is a "erase, write". So here is the deal - if a mke2fs filesystem is created, that means for /data and /cache that the bootloader is actually mounting those partitions (as ext4 filesystems) and restoring into them file by file. Otherwise, a "blob"-type write would just overwrite the newly created ext4 filesystem metadata.
/system is handled differently though - notice in the factory install logs there is no detail about filesystem creation for the /system partition? That's because Google is using a "sparse ext4 image" format for the system.img file, and it can actually write this to the /system partition as a binary blob.
So, on the chance that there is something wrong with the system partition, why don't you manually create the /system filesystem by hand to see if any errors occur? e.g.
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
If this proceeds without error, try installing a dev ROM (not a factory ROM) and see if you can get further along.
The one thing which is fortunate about your situation is that you can return your device through flashing to complete factory stock, including locking the bootloader... if returning the device (via a warranty return/RMA) process is an option for you.
Whew that was a lot of typing. I think I am done for the day.
bftb0
bftb0 said:
That video is an unusual bootloop. With "normal" bootloops the kernel stays up and the android layer cycles endlessly in it's startup checks - but your video looks much more like a kernel panic occurs, as the screen goes back to a bootloader display.
Click to expand...
Click to collapse
This is the bootloop occurring once after doing fastboot oem lock / fastboot oem unlock - after the next reboot it stays at the Google logo without rebooting again.
(1) perform soft-boots of the recovery with fastboot, ... As this requires no writing nor reading of the eMMC Flash memory, if it fails to setup the display correctly, perhaps you have a hardware problem that is unrelated to flash memory. (As you tried multiple recoveries, you may have already done this - it wasn't evident whether you flashed your different recoveries or soft-booted them)
Click to expand...
Click to collapse
some were soft-boots some were with flashing of recovery, but CWM recovery hangs in either boot type after mount /sdcard or mount /user and mount /system.
I also tried some different versions of openrecovery-twrp-XXXX-grouper.img and none of it would start up.
Note also that you can run several adb sessions simultaneously, so in separate windows with the recovery running you can certainly be doing
C:\fubar> adb shell logcat > logcat_output.txt
and
C:\fubar> adb shell cat /proc/kmsg > kernel_log_output.txt
Click to expand...
Click to collapse
Ok, when I am in recovery I can mount /system and use /system/bin/logcat but there are only three lines with "scanline" something (do you need this?)
(2) see if anything is leftover in /proc/last_kmsg on the boot cycle immediately following the "bootloop". It might be possible to jump the device into fastboot mode by pressing Vol-Down the moment the Google logo first reappears. From there, soft-boot a recovery and capture the output of
adb shell cat /proc/last_kmsg
Click to expand...
Click to collapse
I couldn't go to fastboot when the Google logo appears but last_kmsg is this -> http://pastebin.com/VkmNdM5d
After oem lock / oem unlock and the reboot (like in the video) I managed to get into fastboot and recovery, here is the last_kmsg -> http://pastebin.com/wR1yptWr
(3) Start your adb server on the PC and launch the "bootloop" and see if you can get a shell before the crash occurs. If you can get one before the crash occurs maybe you will be lucky enough to catch a problem via
adb shell cat /proc/kmsg or adb logcat -v threadtime
Click to expand...
Click to collapse
nope. wasn't able to get a shell although I activated debugging with your procedure:
Note that if you have installed a fresh ROM, you can toggle ADB debugging on by mounting /data and
# mkdir /data/property
# chmod 700 /data/property
# echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
# chmod 600 /data/property/persist.sys.usb.config
Click to expand...
Click to collapse
Still no adb while stuck at Google logo
/system is handled differently though - notice in the factory install logs there is no detail about filesystem creation for the /system partition? That's because Google is using a "sparse ext4 image" format for the system.img file, and it can actually write this to the /system partition as a binary blob.
So, on the chance that there is something wrong with the system partition, why don't you manually create the /system filesystem by hand to see if any errors occur? e.g.
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
If this proceeds without error, try installing a dev ROM (not a factory ROM) and see if you can get further along.
Click to expand...
Click to collapse
wow - why would they do that? Anyway, I flashed recovery-clockwork-6.0.2.3-grouper.img and was able to format:
Code:
~ # mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs -T ext4 -m 0 /dev/block/mmcblk0p3
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
41664 inodes, 166400 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=171966464
6 block groups
32768 blocks per group, 32768 fragments per group
6944 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 39 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
and with adb sideload tried to install pa_grouper-3.00-09FEB2013-203806.zip. But it stopped at "Installing update..." (the cat /proc/kmsg is here: http://pastebin.com/rjd3b1iZ). I tried it again and again it stopped at Installing update, and here is the last_kmsg and the kmsg again: http://pastebin.com/gPBe7JFD and http://pastebin.com/uXHbX3we.
The one thing which is fortunate about your situation is that you can return your device through flashing to complete factory stock, including locking the bootloader... if returning the device (via a warranty return/RMA) process is an option for you.
Click to expand...
Click to collapse
Since everything failed I guess that's my only option, unless there is something in the logs ... maybe you could take another look?
Whew that was a lot of typing. I think I am done for the day.
Click to expand...
Click to collapse
And I am very thankful for your help!
aha,
I am travelling now, so there is a bunch of stuff I can't do easily right now... but I will have a look at the pastebins to see if anything jumps out at me.
Stay tuned.
aha27,
I looked at your pastebins. The only thing that seemed odd was the complaints about the cache partition (mmcblk0p4) in the kmsg logs. But it only appeared one time - hardly compelling.
The only other thing I could suggest is perhaps look in the recovery logs ( /cache/recovery/recovery.log or /tmp/recovery.log) for the recoveries that hang (but you can still communicate with). Maybe there are some crumbs in there that will put you on the correct trail.
FWIW, when I boot my N7 (JOP40D), it does take quite a bit of time for adb to come up - so if the initial OS boot was getting wedged before that happened maybe that explains why you are not seeing it even though you diddled with /data/property/persist....
I haven't looked into this, but is it possible to modify default.prop in the ramdisk so that the adb service gets started earlier? You would have to unpack & repack a boot image to do this. Actually, now that I think of it, you could just modify the "adbd" service definition in the /init.rc file in the ramdisk so that adb is not contingent on a getvar/setvar variable. Perhaps that would get adb running earlier in the OS boots that are hanging, and you might have a chance of observing more things.
I seem to be running out of ideas. With a lot more work, you could implement all sorts of unattended/blind captures though. For instance, a "one-shot" service definition can call a script that starts yet another script - but puts the 2nd one into the background. That way the oneshot service does not block init - and the second script can do strange things such as periodically record dmesg output or logcat output into files in /tmp and then copy them to the /sdcard once it is mounted. This would give you a way to observe stuff going on in the Android boot (after the fact) even if you can't gain realtime access via adb. But, this does require that you unpack, modify, and re-pack boot images.
Well, there's a few ideas. They seem to require progressively more work, though.
Good luck with your tab.
Thanks thanks thanks, but ...
Thank you very very much for the time you invested in my problem, :good:
but this:
bftb0 said:
aha27,
I haven't looked into this, but is it possible to modify default.prop in the ramdisk so that the adb service gets started earlier? You would have to unpack & repack a boot image to do this. Actually, now that I think of it, you could just modify the "adbd" service definition in the /init.rc file in the ramdisk so that adb is not contingent on a getvar/setvar variable. Perhaps that would get adb running earlier in the OS boots that are hanging, and you might have a chance of observing more things.
I seem to be running out of ideas. With a lot more work, you could implement all sorts of unattended/blind captures though. For instance, a "one-shot" service definition can call a script that starts yet another script - but puts the 2nd one into the background. That way the oneshot service does not block init - and the second script can do strange things such as periodically record dmesg output or logcat output into files in /tmp and then copy them to the /sdcard once it is mounted. This would give you a way to observe stuff going on in the Android boot (after the fact) even if you can't gain realtime access via adb. But, this does require that you unpack, modify, and re-pack boot images.
Click to expand...
Click to collapse
is too time consuming for me and as the tab is not too old, I will reflash it with stock, lock it and send it back. Initially I thought it could be solved, then I hoped that you could help me proving it is a hardware problem, so I'd have no problem getting it replaced, but let's see what Google tells me.
Good luck with your tab.
Click to expand...
Click to collapse
Thank you. Although it is off-topic: I talked to Google support (Germany) and they were absolutely not helpful. On the contrary, after I told them that I unlocked it to flash the previous image they told me, that as I have voided my waranty the could not guarantee that the tab will be replaced. And: they won't tell me (even after I asked twice), which options I'll have and what they will costcost, if it's a problem due to unlocking thus not covered by guarantee. That was no nice exceperience so far.
Well, if it turns out that Google/Asus refuses to do anything for you (seems hard to imagine, but I suppose all things are possible) and they return the tablet to you in the same condition, send me a PM or come back to this thread.
best
bftb0 said:
Well, if it turns out that Google/Asus refuses to do anything for you (seems hard to imagine, but I suppose all things are possible) and they return the tablet to you in the same condition, send me a PM or come back to this thread.
best
Click to expand...
Click to collapse
Hi I have almost the same problem, the thing is I'm using Mac and i don't have pc.
And my mac can't recognize my n7. I have installed TWRP v2.4.3.0
Please advice me.
Thank you
coszy said:
Hi I have almost the same problem, the thing is I'm using Mac and i don't have pc.
And my mac can't recognize my n7. I have installed TWRP v2.4.3.0
Please advice me.
Thank you
Click to expand...
Click to collapse
fastboot and adb work perfectly on the Mac.
http://developer.android.com/sdk/index.html
In fact, of the three platforms (Windows, Linux, Mac) setting up fastboot/adb on the Mac requires the least effort.
stuck on google logo after factory reset
My Nexus 7 locked up, got it to the recovery screen and did a factory reset. now I am stuck in a loop... it opens to the black screen with GOOGLE and stays there. I can get it to the bootloader screen but nothing more. Help please... I am NOT tech saavy!
mac20132 said:
My Nexus 7 locked up, got it to the recovery screen and did a factory reset. now I am stuck in a loop... it opens to the black screen with GOOGLE and stays there. I can get it to the bootloader screen but nothing more. Help please... I am NOT tech saavy!
Click to expand...
Click to collapse
I sent mine to Google and got a new one ...