Related
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Uh, did you remove the back cover and remove/replace the battery?
Glycerin50 said:
First some history with my G1:
I used the normal unrooted G1 for about a ear after i decided to root it. I rooted it succesfully to 5.something (old, because there wasnt ADW launcher yet). Soon after i wanted to go 2.2 or cyanogen 6.0.3. That too was a succes, but after short use it turned out quite slow. I did some research and found out that 5.0.8 is the way to go for a fast G1 phone ith use of apps. Short install but a few trial and errors (lots of factory resets etc.) i got it running smooth. I installed all my apps once again and thought to myself "i should do a Nandroid back-up before i have to wipe it all again...". So i remembered ROM Manager from 6.0.3 and installed it from market. I did a backup via there, but as i clicked i saw a message for a milisecond. It seemed like an error message, but after a split second my phone just rebooted.... Only this time it got stuck at the G1 boot logo....
After getting familiar with Cyanogen this was very new to me. I tried going into recovery obviousley, but that didnt boot. Only thing that did boot was Fast Boot. No idea what i can do there so i didnt touch it.
More research came i decided that i phone maybe bricked... I found out that you can try Terminal or something in fast boot to reflash something... This still isnt clear to me, and i was wondering if there is any guide that i couldnt find that gives me a noobie guide on how to use terminal on your computer to flash something on your phone?
Thanks very much in advanced!
Summary of things i use/did:
Computer: Macbook 1.0.6 OSX
Phone: G1 rooted to 5.0.8 Cyanogen (stable)
Possible cause: Using ROM Manager to make a Nandroid backup
Click to expand...
Click to collapse
Rom manager has a habit of breaking recoveries. If you can get into fastboot you can flash a new recovery from there. If you have an engineering spl that is. Need your info from fastboot. Do you have danger spl? Amonra has guides on how to flash from fastboot. Get his 1.7.0 and fastboot flash it. You dont sound bricked.
http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Ok been a while ,sorry! I am still "bricked" (or at least i think i am). Yes i have taken out the battery and putting it back in.
@Johnson: Yes so i have read! A little to late, My info from fastboot:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
I'll go to that tutorial ,see if i can figure it out. Thanks for the help!
EDIT: So, ive read it... But its not clear to me. Do i need to open a terminal like program on my mac and just type in:
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
Or do i need to connect with my phone somehow (besides USB)
Yes, boot in to the SPl (you might need to enable fastboot in there, just poke stuff), then fire up Terminal.app, cd to the /tools directory where the SDK is installed, then issue the commands.
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Boot to fastboot mode. Should tell u how on amonra's page. Put recovery in tools folder of your sdk. Then open command prompt on PC and type: fastboot devices hit enter. Should get a serial number. CD to tools folder and type fastboot flash image command in thread
Sent from my HTC Magic SparksMod using XDA App
Glycerin50 said:
I havent heard of SPL boot yet, how do i do this? Or is this Camer+power on/off?
Also the part about Terminal.app is total abracadabra to mee, haha. ill try and figure it out using the tutorial and maybe some common sense. If i did figure it out, i'll let you guys know!
Otherwise, if u read this and feel like helping... Much appreciated! I can use all the help you can offer!
Thanks!
Tobias
Click to expand...
Click to collapse
Yes, the SPL is the bootloader (camera+power). To open the terminal, got to Applications > Utilities > Terminal.
ok, this is getting more and more understandable to me
Just where is this tools SDK folder. Will this apear on my pc when i plug my phone while i bootloader? or do i need to download some more stuff for this all to work on my pc...
U will need to look up how to install sdk on your computer. Its another program u need to control your phone with the PC. Called adb. Android debugging bridge
Sent from my HTC Magic SparksMod using XDA App
I don't think that fastboot comes with the SDK. There is fastboot-mac zip file somewhere out there... I can't remember where I got mine from, but there is one here http://developer.htc.com/adp.html
Put the file somewhere on your mac and use the terminal program in your applications/utilites folder to access it. You should be a little familiar with Linux to use it If you want to get fancy, put it in /usr/sbin or somewhere in your $path.
The SDK kit is good too, especially adb.
EDIT:
Here are a few good threads to get you headed down the path to flash-a-rama. Most of the commands are the same, regardless of platform, but the installation procedure will vary, i.e., fastboot erase system -w does the same thing on any platform.
http://forum.xda-developers.com/showthread.php?t=517874
http://forum.xda-developers.com/showthread.php?t=532719
Lastly this thread should be required reading... http://forum.xda-developers.com/showthread.php?t=655097
SUCCES! YEAH!!! Thank you guys so much! While reading your posts and all the guides i decided to get into bootcamp (windows on mac) and do it all there.
It was way easy to install and ive setup adb and SDK easy and used fastboot to flash Amon Ra's recovery!
It installed within seconds and from recovery i did a fresh wipe and installed my 5.0.8 cyanogen.
Right now it booting up for the first time as i typ and i think its going to boot.... Yes, it takes a long time the first time.
Yes, it works!
Thank you guys again!
Tobias
I bricked my moto x with safestrap. I'm stuck in a boot loop that I can not get out of, nor can I get SS to pop up. The best I can do is get into fastboot and send commands to the phone. I've tried searching but I can't find the commands to pull data from the phone, nor do I know exactly what the path/directory would be where my nandroids are saved.
I have about 3 years of info/apps on this phone that I have been migrating over from phone to phone. It would be a real shame if I had to start over from scratch again over something so dumb. I did everything by the book. I had SS working, I made my nandroid. I created rom slot one and installed. Now bootloop. I never imagined that I would not be able to get back into SS. SS is supposed to be safer than even CWM/TWRP, and as it turns out its the most dangerous thing I've ever used. I have NEVER been put into a situation where I couldn't recover and had to fxz and wipe data. And I've had over 15 android phones.
My issue is that I just don't know the code to extract the data using adb. I can get the phone to reboot when in fastboot using commands on the comp, but thats the extent of my knowledge. Please help.
You obviously didn't search. Try harder. Multiple threads.
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
You obviously didn't search. Try harder. Multiple threads.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Thank you. I am unable to issue commands to the phone through adb. I don't know if its becaues I am doing something wrong or not. I have the commands. They do not work. I'm not sure if the phone can accept adb commands through fastboot. The only way I know out of this is to FXZ, but that wipes the phone and I am trying to use that as a last resort.
The toolkit can reboot the phone and reboot into fastboot, so I assume that adb commands work. However, when I try to use adb it doesn't even show as a device. I'm doing something wrong and need help.
***Edit***
Phone not even showing up in RSD lite. May have to use home comp. This laptop is windows 8.1
Fastboot the system.IMG then move everything to your PC you want to keep then run rsd, or delete the delete user data line in rsd then when running move everything to PC the run full rsd. I've been stuck in this loop many times and you can get the system back but in order to get ss running again your going to have to do a full fxz restore
shane1 said:
Fastboot the system.IMG then move everything to your PC you want to keep then run rsd, or delete the delete user data line in rsd then when running move everything to PC the run full rsd. I've been stuck in this loop many times and you can get the system back but in order to get ss running again your going to have to do a full fxz restore
Click to expand...
Click to collapse
Pm sent!
[email protected] hangouts much easier
shane1 said:
[email protected] hangouts much easier
Click to expand...
Click to collapse
Message sent
Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.
When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.
If you've familiar with this problem and can direct me to regaining factory settings I'd greatly appreciate.
Used Nexus Toolkit to root, an had Twrp recovery. Had no backup w/Toolkit but did have a Nandroid backup....to no avail. Can't access it..
I still can get to bootloader and recovery of course but have a "NO OS" sign on the device.
A step by step from anyone in the community greatly appreciated.
Thanks
You could flash the system image through the root toolkit
I used wugs. And as long as you are boot loader unlocked and can access boot loader you are good. I somehow magaed to delete my OS, and my recovery so nothing worked! Used wigs, clicked flash stock and unroot. Checked the box for soft bricked or bootloop and it downloaded everything and flashed it onto my phone and it was fixed in 5 mins!
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
Additionally if you plug your phone into a comp while in recovery it should mount the storage on your PC so you could always dl a ROM on PC and move it over then flash.
Yea use wugs toolkit to flash back to stock. Easy fix
See this thread:
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Wow the wugs toolkit is amazing. Thanks
This is exactly why I dislike toolkits... They're written by others, and you can never be 100% certain what's going on under the hood. I personally find it easier to simply run the fastboot and adb commands, and be done with it... If you make a command line mistake, the image simply won't flash, in which case, your system is left untouched. If you make a mistake with a toolkit, you could end up with a very expensive brick on your hands.
I'm in no way trying to denigrate toolkit devs or users; I'm simply giving my opinion on what I find to be the easiest, most risk-free method for flashing factory images and boot images. Recoveries are fine for day-to-day zip flashing, but when I need to do a bit more, I find fastboot and adb are the way to go. ?
jjhiza said:
This is exactly why I dislike toolkits... They're written by others, and you can never be 100% certain what's going on under the hood. I personally find it easier to simply run the fastboot and adb commands, and be done with it... If you make a command line mistake, the image simply won't flash, in which case, your system is left untouched. If you make a mistake with a toolkit, you could end up with a very expensive brick on your hands.
I'm in no way trying to denigrate toolkit devs or users; I'm simply giving my opinion on what I find to be the easiest, most risk-free method for flashing factory images and boot images. Recoveries are fine for day-to-day zip flashing, but when I need to do a bit more, I find fastboot and adb are the way to go. ?
Click to expand...
Click to collapse
To elaborate more on this, http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
I completely agree with jihiza here 100%
Its essential learning how to use adb/fastboot. Its not difficult to do and pays off in the long run.
how did you get your computer to recognize the device? Everything I've tried to this point says "no adb device"
edit: I got everything to flash manually.
papi5120 said:
You could flash the system image through the root toolkit
Click to expand...
Click to collapse
Or you could just fastboot it Root Toolkits make zero sense to me. Takes longer to Download the toolkit than it does to just fastboot the device.
Toolkits are great for phones that are good for phones with out fastboot but a nexus I feel that people never learn how or why they work stuff like this happens people don't know what to do.
I have wiped the System partition before, usually on purpose when flashing a ROM. There have been a few times that I either thought I had a backup which turns out I didn't, or the ROM I downloaded is in a mysterious "0" folder that twrp refuses to see. It's inconvenient yet but easy fix.
Use twrp to adbsideload if you have a ROM saved to your computer of I can fastboot factory image. No need to panic worst case scenario I don't have a phone for a day I do this with no computer and am gone for extended period of time
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
mikeos89 said:
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
Click to expand...
Click to collapse
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
mikeprius said:
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
Click to expand...
Click to collapse
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Can't you just drag and drop a ROM and gapps while in twrp... Ive.done it before...good luck
Not likely as the phone plugged into the computer may not read it as a "USB" drive. I have windows and I have no idea what the command prompts are for Mac. Also if your understanding is virtually nothing, you need at least understand the basics of fastboot and custom recovery in order to fix your situation.
The good news is that your phone isn't messed up. The bad news is you need to roll up your sleeves and learn the basics of how the commands work so you can reboot the phone back. Everyone here can describe to you what to do but since you don't know the fundamentals it won't mean anything until you do. Sorry.
Btw, jailbreaking isn't the Apple version of "root". They are 2 completely different things.
What I would do is fastboot erase TWRP and re-flash it as it sounds like you are having problems, then adb pull a custom ROM into your internal storage. Reboot into TWRP and flash it. That's what you need to do.
mikeos89 said:
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Click to expand...
Click to collapse
I don't know anything about flashing a phone from a Mac but if you can boot your phone into bootloader mode and get fastboot to work on the Mac I would follow the steps under Step 5, Method 2 at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I use that method to upgrade my phone every time a new ROM comes out and it works great.
Note:
1. You this will get you back to stock, you'll still have to flash your custom ROM after you get your phone working.
2. The .img files can be downloaded from https://developers.google.com/android/nexus/images#shamu.
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
bushako said:
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This, easiest way for you probably. I've done it this way before too. I suppose you could ask someone to TeamView your pc, but you should probably try the usb otg method first.