Related
Hi,
i have question, when i root my G1 and flash CyanogenMod or an other custom image/rom, can i also flash the newest official T-Mobile OS Release Rom???
So i have none disadvantages with rooting compare to not rooting, or???
ScorqYoN
No. You cannot. You can't flash two ROMs at the same time.
That said... Everything in the latest official Tmo release is in CyanogenMod, with the exception of the IM app in his latest build (I guess he found out it was proprietary? I dunno why). But you can drop that in from another build easily (pm me if you need help), so you will have no disadvantages.
Honestly, there are no disadvantages to rooting, as long as you do it right. But if you're totally new at it, instead of CyanogenMod, try WesGarner Build. The one without the RAM hack. It's almost exactly like Cyanogen's, but easier to flash, because you don't have to do the HTC image first. It's a good newbie ROM.
No i don't mean second roms on one time...
The possibility to flash the normal T-Mobile img back with root acces?
The IM App I doesn't need because I don't
use google talk.
Can i also delete **** Apps like Web'n Walk or other Commercial of T-Mobile or Google, when i have rooted my phone??
What do you mean with with HTC Image? The recovery.img???
And what with Ram Hack????
But the Cyanogen is the most stable and fastest rom or???
And he have full themes of Hero etc..
I have read many tutorials of rooting so i'm familiar with the most things...
Only one thing: Apps2SD, Radio and SPL do i flash at last or???
And what first APPS2SD or RADIO AND SPL?
Where i became the really "up to datest" RADIO AND SPL???
Last Question: Can I loose root anywhere or not??? Because I don't want to root the phone twice...
If what you want is the official T-Mobile build w/ root access, enomther has a good rom with exactly that, and each time T-Mobile send out an update, the ROM gets updated accoringly and there's also an expansion pack that includes the things that "root" users have come to love like apps2sd & tether and what have you, you can check that out here
Yes you can remove unnecessary apps through the terminal emulator or using ADB
If you've read up on installing Cyangogen as you said you've been reading up on rooting, the HTC image is the Developer image that you flash to your phone first, so the first time you flash Cyanogen it can back up and restore all the proprietary Google apps that Cyanogen no longer Distributes
The RAM hack adds ~10MB of space to your phone, but takes aways from the video, so if you play any 3D games they will be rather laggy or possibly unplayable
Cyanogen being the most stable or fastest - It's my favorite ROM, and it's definately by far one of the more popular. Fastest, Most Stable though will depend on what apps you put on your phone and how you use, so if Cyanogen doesn't work out for you, try another. I doubt you'll be dissapointed after tryin one though
If you're doing the radio & spl, after you get root access and have the custom recovery you can boot into flash radio first, reboot, then spl reboot, apps2sd is automatic in all ROM's that include it
No you can't really loose root, you'd have to downgrade and reflash an official T-Mobile image and go back to stock to loose root
Ok, thanks.
So i think i root my phone, because i think they are almost only advantages.
What is terminal emulator and is it easier then adb for removing unnecessary apps???
Optionally, i want to play 3D games... I don't unterstand why the 10mb from the internal space of the phone. When I have APPS2SD I think I have enough space...
All in all, i think i flash first with CyanogenMod Tutorial and CyanogenRecovery.img+Cyanogen Rom... and after that i can try many other Roms... like http://unslaved.think-android.com/ or one in this list http://db.androidspin.com/android_build_information.asp ...
So, downgrade->root->recovery.img->radio->spl->and then custom rom???
Other question: When is a wipe necessary??? With every update??? Cyanogen has the advantage of a instant Updater...
But what is with other roms... when i have to wipe and how???
ScorqYoN
PS: Sorry for my bad english, I'm german.
Teminal Emulator is just a terminal you can open up from your phone, I prefer using ADB, but you should be able to accomplish the same task either way
One thing I forgot to mention about apps2sd, although moving the apps to the sd is automatic you have to manually setup your ext2/3/4 partition, if you're gonna use the Cyanogen Recovery as you've stated you can follow this guide to do so
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
you would partition your card anytime after you have Cyanogen's recovery and before you flash your rom
Yes the steps you posted are in the right order
Wipe is necessary when switching roms, the first time you go to Cyanogen and anytime you switch to another rom, you don't have to wipe if you're updating to a newer build of the same rom you're using unless the dev specifically says to.
To wipe you'll want to boot into recovery, you'll see an option to wipe from there
Also you'll want to clear everything in your ext partition, so while in recovery choose the option to go to console and use the commands below
Code:
# mount -o rw /dev/block/mmcblk0p2 /system/sd
(enter)
# rm -rf /system/sd/*
(enter)
# rm -rf /system/data/*
(enter)
# reboot recovery
Thank for your support , i'm new in the android scene and get the g1 few days ago...
Ok, with the Wipe and Roms i unterstand.
But with the Partition and so seem to be very complicated...
At the moment i have the in package of g1 SanDisk 2GB SD Card.
So the ram hack isn't necessary or? Because i want the option to play 3D games...
And partitions on SD can i make later or???
But without them i can't use Apps2SD??
Another Questions: How do I backup my contacts,apps,settings... before wipe or flash an other rom???
I've heard from a app called "Backup for root users", but i don't find it on the market... (Many apps read in the internet i don't find in the market, strange...)
When i plug my G1 with USB on my PC, and it detected with ADB Interface, i have a ADB connection or?
So then i have to cmd: "adb shell" and it say:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
-> So then i have a ADB connection???
Partitioning the card is really easy if you give it a read through then go through the steps
Alternatively if you use Amon_RA's Recovery instead of Cyanogen's you can setup you're ext partition automatically, his recovery image can be found here
No the RAM hack isn't necessary, and it's not part of Cyanogen's build
Yes you can make the partition's later, but without an ext partition apps2sd will not be used, the ext partition is necessary for apps2sd
For you last question, contacts will sync automatically with your google account, as for the apps and setting, I've never tried this, so someone else will have to chime in or you could search for it, I've never found terribly painfull to reinstall the handfull of apps I use and change my setting for wireless etc ... back to what I want
So the recovery img hasn't relation to rom???
So whats the most recommendable recovery img???
Can i update or switch recovery img after flashing rom so stay in all except recovery img??
And have i a 100% functional ADB connection???
Last imporant question: How do i get acces on my sd over my g1 for format, downgrading etc., because at the moment i haven't a card reader...
No you can use either Recovery image it has nothing to do with the rom
Amon_RA's has more options than Cyanogen's, which probably makes it a bit more user friendly, especially towards the noobs.
Yes you can switch between recovery images without affecting the rom
THANKS, although i have few questions left...^^
When i plug my G1 with USB on my PC, and it detected with ADB Interface, i have a ADB connection or?
So then i have to cmd: "adb shell" and it say:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
-> So then i have a ADB connection???
Another very imporant question: How do i get acces on my sd over my g1 for format, downgrading etc., because at the moment i haven't a card reader...
The error says it's not finding your device
Make sure on your phone you go to Settings -> Applications -> Development and check the box for USB Debugging
Make sure all the drivers are installed properly, go into the device manager on you computer and make sure there are no "yellow exclamation point"
Then try to use adb shell again, report back if you're still getting an error
Using the guide I linked you to, or using Amon_RA's recovery the card will be partitioned/formatted while in the phone, you won't need a card reader to accomplish this.
For adding your downgrade file you can turn on USB Mass Storage from your stock rom and place your downgrade file & your recovery image on your sdcard
Once you flash your recovery which based on your circumstances you should definately be Amon_RA's recovery because it has an option for USB-MS toggle which will turn on the USB Mass Storage, so you can add all your zip files for your updates to your sdcard after formatting & partitioning straight from recovery. So it sounding more and more like you should go with Amon_RA's recovery
Ok so i think i take Amon Ra's recovery img, because it partitions my sd card for apps2sd and has many other advantages, also for beginners, or???
So i can take this tutorial http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod and when i have to use the cyanogen recovery.img, i use Amon RA's Recovery.img, or???
But how do i do that:
"For adding your downgrade file you can turn on USB Mass Storage from your stock rom and place your downgrade file & your recovery image on your sdcard"
Now i have activate USB Debug and install the driver and its all detected with ADB...
But still no device found..
Do i have to be in a certain mode, because i am in normal home screen...
I also need ADB for login after downgrading with wifi, because i haven't umts/gprs... http://modmygphone.com/forums/showpost.php?p=51891&postcount=12|
So, when i have ADB connection i start downgrading.
Yes when you get to the part of the guide that says
flash_image recovery /sdcard/cm-recovery-1.4.img [enter]
replace with:
flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
When you plug your phone into you computer it will ask if you want to mount, that's what I meant by mass storage device, you can add it like that
Ok now i think all understand!!
Except working ADB... do i have to be in a certain mode like recovery or something else for ADB, because i'm at homescreen...
jackslim said:
The error says it's not finding your device
Make sure on your phone you go to Settings -> Applications -> Development and check the box for USB Debugging
Make sure all the drivers are installed properly, go into the device manager on you computer and make sure there are no "yellow exclamation point"
Then try to use adb shell again, report back if you're still getting an error
Click to expand...
Click to collapse
Did you make sure to check those things for ADB, once everything is installed correctly ADB will work from the home screen
The two things I pointed out are the most common mistakes in setting up ADB if you're still having issues refer to this thread
http://forum.xda-developers.com/showthread.php?t=532719
It should be able to get you up & running with ADB
Ahhh, nice it work!
I completely disinstalled the driver and all and tried then with your posted tutorial and now it work it found a device under adb devices and adb shell work,too!
So ADB i use for login with wifi, delete apps like web'n walk etc. and what else?
Is their a tut for deleting "undeletable apps, or aren't these apps, like web'n walk not in custom roms??
I have a problem with downgrading...
When i put the dreaimg.nbh on my formatted sd card and start the phone in bootloader it said: "Loading...", "Checking...", "not allow"... then the multicoloured screen in the middle "serial 0"
I read that i have to make my sd card to goldcard, so i think i try it...
ScorqYoN said:
I have a problem with downgrading...
When i put the dreaimg.nbh on my formatted sd card and start the phone in bootloader it said: "Loading...", "Checking...", "not allow"... then the multicoloured screen in the middle "serial 0"
I read that i have to make my sd card to goldcard, so i think i try it...
Click to expand...
Click to collapse
Why are you downgrading if you have root?
The purpose of this document is to clarify a few basics about HTC Android Phones and basic commands to interface with the phones. Think of this as a beginner's guides to the Android device from a non-traditional user's point of view. I'll keep it simple and plain as much as I can for the new users. I'll also try to keep all the technical aspects true as much as I can while keeping it simple.
Before you go on, please read this and understand the basic concepts and how and why following commands are being used. Do not follow anyone's instructions/tutorials/guides without prior basic understanding of what each command do. I do want to believe it's humans visiting this forum and not lemmings. If you do not understand, feel free to ask here. I will or someone else also knowledgeable will answer your questions. DO NOT QUOTE THIS AS A WHOLE. My pet peeves and a complete waste of screen space.
Sometime, depending on your OS, command names may change (e.g: mouse / mouse.exe / mouse-linux / mouse-mac). For general purpose, we'll use mouse instead of an OS specific commands in this instructions.
So to repeat myself, if you understood the concepts of the commands, and you are on a linux system and someone's guide says touch index.php, you will automatically type touch-linux or whatever the name of your executable is on your system.
We shall assume you know how to install needed drivers and where to get android sdk and put the sdk binaries (executables) in the system path. If we need to expend this let me know and I'll expend this here.
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA. Note: By replacing your recovery image, you may not be able to have OTA updates.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
How do I know the phone is bricked? A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
If anyone needs me to dig deep into using anything else, please PM me. I'll add it on here. Hopefully this will help all newbies about the basic commands and what they do.
FAQs (UPDATED Feb 09, 2010)
Q: One question about the Android SDK. Do I need it to flash my N1 or just to program new apps? Where can I get it?
A: Android SDK is not entirely needed to flash the N1. However, there are tools in there that you need. Adb / Fastboot etc. Although they can be downloaded by themselves, the windows version of the SDK also have the Drivers that are needed for android devices for USB connection. So, it is recommended to get it. You can get it from developer.android.com
Q:I have never experienced anything like this when I did a hard-spl on my winmo phone. Radio versions are included with SPL's, right?
A: Official packages from HTC did come with nbh packaging, meaning it is a all in one upgrader that will update Radio, ROM, System etc, it is very much common for active development area here at XDA to get the radio or SPL or ROM separately and independently of one another. And as such, you will most likely flash them seperately (who wants to wait 6-8 months). Also, since this phone is released by google, HTC will most likely not update any major Radios. However, it is very likely that we will be hacking in Radio updates or any other "updates" from HTC from their new device - HTC Bravo.
Q: Is there a guide for snow leopard? I'm kind of stuck.
A: I personally ran android SDK and aforementioned executable on both MAC OS 10.5 and 10.6. Like I posted, the commands and the executable names may be slightly different. I may call adb and you may find it as adb-mac. I am not going to write 3 separate documents for 3 separate OSes. You have to know that adb=adb-mac (on your mac), adb-linux (for linux) etc. And yes the above guide will work universally.
Q: Can i replace the splash image..?? (unlocking related)
A: As of the above date (next to the FAQ) no you can not. Issue is probably a few folds. One of them is that splash1.img is not going in due to security lock. Remember, you unlocked the phone. HTC will not like it. Anyhow, I like the current quad color X. If you are thinking of getting rid of the lock logo, good luck. Even if you can get rid of it, you will still have to overcome the pink text that says ***UNLOCKED*** on your bootloader.
Q: Can you run Windows Mobile on Android Phones?
A: With enough resources given, sure. Will it ever happen? No. Why? Windows mobile compiler and builder cost $. As a matter of fact, as of version 5, it was going to cost me $75 per device. That's one of the reasons why handset makers went to Android open platform. Android is free and universal so as long as you use certain chipsets and certain items, you are good to go. Can it ever be ported? Sure. With right amount of time and money anything can be done. But at this point, it's cheaper for you to go buy a windows mobile smartphone.
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Q: I have installed the Android SDK however, i cannot seem to get the laptop to detect the nexus. What have i left out?
A: Most common item that people forget to enable is USB Debugging. Settings => Applications => Development => USB debugging [checked]
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Q: Which step of the rooting / recovery procedure does it give root?
A: Root and Recovery are two totally different things. Recovery is a partition that contain recovery information. Stock recovery is what allows OTA updates etc. Normally it will search for update.zip in the root folder of the SD card. Amon_RA's Recovery or any other recovery images are there to enhance the traditional stock recovery. Amon Ra's Recovery for example, contains thing such as ability to update from different zip files, and backup/restore of your data/system.
Rooting is not done by recovery but is a kernel level access (simply put) that will give root or "SU". It is done by patching the boot partition of the your android device.
Q: What are the differences, advantages, disadvantages of the different ROM's?
A: They are all different. Some have some features, some are plain stock, some are made for bleeding edge kernel etc. You'll have to try them out and figure out yourself. I may make a chart of what they are (see the bottom at my signature - wiki) but with too many android devices, I will need some major help. One person alone will not have total knowledge of all the ROM releases. There are just way too many devices and ROMs.
Q: Which ROM will allow OTA updates?
A: Stock ROM WITH Stock Recovery.
Q: If the phone is SIM/carrier unlocked and you root do you have to SIM unlock again?
A: SIM/Carrier unlock has nothing to do with rooting your phone. You can still have root and still be carrier locked. Nexus One comes carrier unlocked from factory.
Q: How much space is there for apps? is using the sd card really necessary? (on Nexus One)
A: Search google? The phone has 512MB or space. That SHOULD be more than enough for you. If not, you have some serious issues. I do not believe you will not App2SD for Nexus One. Google did say during the release conference that they will update Android/N1 so that apps can be run/installed to SD but that requires some system and security changes (mainly to prevent pirated software - Yes if I write something, I deserve to get paid for it).
Q: When you do "flash zip from sdcard" or "fastboot flash image" does this merge and overwrite the files in to the partition?
A: When you update a software (via recovery), software my be merged. However, if you fastboot flash, just like the word flash says, it will flash and overwrite the partition.
Q: Which partition does "flash zip from sdcard" affect?
A: Depends on what you are flashing. It could be any or all of the partitions such as SPL, Boot, System, Recovery, Radio. You should study first before randomly flashing things.
sorry, got it!
blakestimac said:
i apologize if this is the wrong place for this but, but i have adb setup perfectly, but fastboot is not recognized at all. could i have missed something?
Click to expand...
Click to collapse
I need your system info.
What os are you running? where did you get fastboot? what are you trying to do?
Don't forget fastboot boot for testing images. My most used command
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
wishmaker738 said:
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
Click to expand...
Click to collapse
Check the FAQ.
dylanfan424 said:
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
Click to expand...
Click to collapse
Ok. I need to know what you actually did. I am not understanding what you are trying to do.
Can't run adb commands - device not found
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
I'm a noob so can't offer much help...but I would make sure the usb drivers are installed if you're using windows....this probably should have happened when you installed the sdk, but you can also install it through the device manager and point it to the folder where the usb drivers are located. Also make sure the phone is in USB debugging mode. also you may need to reboot your pc. Make sure you have setup running when you run the adb commands. you need to be in the same directory as the adb file, or in the case of the superboot pack you need to type "adb-windows" not just "adb". you may also need to put .exe, ie adb-windows.exe.
pwnvds said:
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Click to expand...
Click to collapse
You run fastboot from the white screen. Android on non-white screen. It's one or the other. It's ADB or Fastboot (depending on the mode of the phone).
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
Is the directory where ADB/fastboot (SDK) is installled in your system path?
I am guessing it's not. If it was, just by typing adb alone (without commands), it'll give you a list of commands. Click here if you want to know how to change your system path to include a particular folder.
We're now in the age of nintendo pilots and point and click OS that no one knows how to use command lines and system paths anymore.
recovery
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
umplarry said:
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
Click to expand...
Click to collapse
Answered in FAQ area.
seraph1024 said:
Answered in FAQ area.
Click to expand...
Click to collapse
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
umplarry said:
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
Click to expand...
Click to collapse
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Click to expand...
Click to collapse
There you go.
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
Thanks for your help
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
I had it downloaded, just had not flashed it
I've been looking all over, but I probably need to check the HTC Dream forum or something.
How do I install a custom ROM? I know you have to adb push update.zip somewhere, but I can't find any info about this. Please help.
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
kmacho714 said:
I was trying to install bad seeds sense 6 and sadly did not back up and did not had any old rom as aback up. the rom installed ok but i got this at the end set_metadata_recursive: some changes failed . the phone just keeps rebooting to twrp. i tried to transfer another rom via adb but im not getting my commands right, any other way to add another rom. or way to update my twrp ? please help?
Click to expand...
Click to collapse
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
twrp sideload
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
kmacho714 said:
sorry but i feel so ignorant. i installed the drivers and have the rom ready, but how to i the phone to adb shell. do i go to mount on twrp or on the advance settings adb sideload? when i put adb shell in the command prompt but it says adb not recognized. i would really appreciate your help if you could help me with more detail if possible.
Click to expand...
Click to collapse
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
adb
tdhite said:
Here's what to do (before having to RUU):
boot into TWRP;
connect USB cable;
adb shell into the device;
Code:
adb shell
see if /sdcard is ok (meaning you didn't mistakenly flash entirely the wrong ROM or something):
Code:
ls /sdcard
if the above shows files is a list of tings you recognize (like Downloads, Ringtones, whatever), two things are ok: i) your data area; and ii) your adb is working, then issue these commands (for good measure):
Code:
umount /system
exit
Using TWRP normally (use the touch screen), Wipe the following: system, cache, dalvik-cache, data;
Now, push a ROM file you want, for now I'd suggest one of the Sense 5.5 ROMs -- at least until the Sense 6 ROMs stabilize a bit more and we've had time to settle out all the new idiosynchrasies). Once downloaded, you'll have some zip file, let's call it "myrom.zip" for the purpose of commands (it'll be something different, just use the actual file name instead of myrom.zip below):
Code:
adb push myrom.zip /sdcard
Using the TWRP touch interface, just install the rom from /sdcard/myrom.zip
Just fyi -- the Sense 6 Roms have been exhibiting some oddities for folks in recoveries -- the issue actually is not the ROM, rather in the ext4 file system and some file system metadata bugs when dropping so many files in one shot as the ROM installer zips are doing. I've been debugging this in my TWRP builds and will be putting an option in to cover for the problem (it's deep in the android of ext4, believe it or not -- the kernel is detecting a problem and remounting the file systems read-only and that's what makes the install fail).
Hope this helps.
Click to expand...
Click to collapse
do i need android sdk? and htc sync? i have the drivers i think? on my device managers it doesnt say adb . just device and on the info it says htc device
thank you
tdhite said:
Goodness -- I thought you were all setup for adb and understood this stuff.
Here's what you need to do *first*, then follow the instructions above after you get adb working. To "adb shell" in to the phone -- you will boot into TWRP, which starts the adb server on the phone. But you use your computer and a "command terminal" window. We have to have this one way or another, so you have to learn. You will plug in your USB cable to the phone and computer, then the commands will work -- yes, they will work with TWRP.
To setup the adb stuff, learn here: http://forum.xda-developers.com/showthread.php?t=2277892 and look for Question 8
Click to expand...
Click to collapse
thanks a lot! those commands work ! just needed to install the drivers . thanks! again
I read many posts and articles the past few hours and realized a few things, would you correct me if they are wrong please.
My phone:
Pixel 4XL, adb reboot recovery gives "no command" it would seem it might have been rooted at some point before I bought it, but now the bootloader is locked and no custom recovery is on it.
Can I not recover data without root?
Saw few articles mention `adb pull' and `dd` to copy block device, which I can't do with no root.
Is it possible to just install busybox with adb and be able to copy block device?
As per this article https://www.andreafortuna.org/2018/...imaging-android-file-system-using-adb-and-dd/
I might have to wait a bit for TWRP as I did upgrade to Android 11 and it seems it is only supports Android 10 at the moment.
In order to put TWRP on my phone I probably need to unlock the bootloader and would that mean lose all user data? Then I really have no hopes of recovering the audio file I'm looking for as then I couldn't decrypt it?
I know the file's mount point and can figure out which block device it was on, but wouldn't the encryption get lost if android was wiped?
Is there a way to get TWRP without factory restore phone, or busybox or something that will help get block devices out.
Someone mentioned that these dm block devices are decrypted, are they? I will attach a screen shot with list of my block devs.
Thanks for any help or pointer, I can't be destroying this phone as I have money on it and other stuff needed for traveling, so I don't even feel like trying to install busybox to see if adb pull would work, and others mentioned if trying to get block dev off the phone while partition is mounted might lose some data, so they advised using TWRP while partition is unmounted and then copy it's image.
I also found this but I would need root, he mentions 'temporary root' is that even a thing?
Extract Android Userdata Partition for Recovery and Forensics - Root101 | Fundamentals of Linux Administration
Open Source and Linux. Guides and Ideas for Designing Highly Available and Scalable Production Environments
www.root101.net
@GogoAkira - Your long, rambling post is very confusing, and you do not clearly state what it is you are trying to do or the current state of your phone. I want to start by saying that if you have not done so already, you need to be on the very latest version of the adb/fastboot binaries. If the phone is working fine and you can access all your files, there are some non-root ways to back up almost all of your data, but you're NOT going to get anything near a nandroid backup. If your phone is working fine on 11 (why would you not be on 12?) you can also enable usb debugging from within the developer options menu and then use it from the RECOVERY mode. You cannot use adb from your PC without first enabling adb debugging. I say this because you claim "adb reboot recovery" won't work. Of course it won't work. You cannot access adb in the FASTBOOT mode. Probably the first thing you need to confirm is that you have enabled USB DEBUGGING and whether or not your ALLOW OEM UNLOCKING toggle can be set to yes. Whether or not you can do this will tell us alot. If it is greyed out in the off position your bootloader is a) currently locked, and b) probably will not be able to be unlocked. Knowing that, then clearly state what it is you are trying to accomplish and people will try to help.
I'm hoping to pull an image of my decrypted /data partition in order to hopefully recover some deleted files via sophisticated recovery software on the PC side of things. I manage to pull an image just fine, but it ends up being encrypted when adb is done pulling it.
From what I can gather doing a lot of google searches when you decrypt in TWRP you're supposed to get a new apparent mount/partition visible under /dev/block or thereabouts. Called "dm-0" on a lot of other phones it seems, but I don't get one of those. Decrypting directly on the phone or via adb works just fine and I can access my /data partition via the shell w/o issues.
However this still ends up being encrypted after pulling it. Is there a way to actually create and pull a decrypted image of said partition this way or am I way off? I need help finding said decrypted and supposed mount point/partition. Can't see anything new under /dev/block or as far as those directories goes so I'm at a loss.
Using:
XZ1 Compact
Android 9
TWRP 3.6.1_9-0
Latest adb from android sdk platform tools as of this writing.
Hmm. Have you tried pulling it while the phone is in recovery? If you are rooted, before pulling have you tried giving root to adb?
adb shell
su
Yes that's what I'm trying to do in order to get a decrypted image. Did not try pulling the image as root. You think that could make a difference?
EDIT: Hold on though. From the shell you can't send adb commands? I.E. opening the terminal with adb shell you have no access to adb?
knerlington said:
Hold on though. From the shell you can't send adb commands? I.E. opening the terminal with adb shell you have no access to adb?
Click to expand...
Click to collapse
adb root
adb remount
Now you're back to adb. Not sure if it will make a difference in this case, but worth a shot.
Also, you could try making a copy of the patrition via TWRP > Advanced > File manager and transferring it to PC regularly from explorer.
I have no problems making an image of said partition in different ways, but the problem is that everything that I need access to from the image file is encrypted despite making the image from twrp after decrypting it.
I'm trying to restore and recover deleted files from this partition, but in order to do that I need an image that I can use in more sophisticated recovery programs.
So is this possible at all or is there a way to decrypt an encrypted image somehow?