I inherited this device, and immediately began tinkering with it, without really understanding too much (bad idea). I flashed the rootable rc29, and then followed the cyanogen wiki's "Full Update - HTC Dream" guide. I also installed DangerSPL.
Everything was working fine, but now I've got a problem. Never knowing when to leave well enough alone, and unwittingly following outdated info, I attempted to flash the engineering bootloader through my recovery menu.
What I have now is a phone that will not progress past the tmobile/g1 splash screen. I have adb access from the splash screen, and can boot into both the bootloader and recovery, but I have no idea how to fix this.
Would flashing rc29 and starting all over solve my problem? I also have a few functional nand backups. Would that solve it? I'm leery of experimenting, since I don't want this to get worse.
Someone smarter than me please save my ass.
Relevant/necessary info?
RA-dream-v1.7.0
HBOOT-1.33.2005
CPLD-4
RADIO-2.22.23.02
Well the good news is all is well (I know you don't believe it yet)
Your only problem is danger spl changes the sizes of some partitions thus you can't boot the old data.
Try the following:
Enter fastboot:
Run on your computer
Code:
fastboot erase boot
fastboot erase system -w
Then boot into recovery and flash either a rom's update.zip(s) as normal (the one you want to install)
Or restore a nandroid backup from your old rom.
Avoid ever flashing rc29 if you have issues and want a clean install the fastboot erase is usually what you need, rc29 returns you to a 1.x radio and bootloader without fastboot.
(BTW most people will tell you just to wipe not the fastboot erase.. however the fastboot erase helps avoid issues down the road)
Well darn, you make it look easy. Thank you for your wonderful, poignant fix, and your incredibly timely response. You've surely saved a lot of hairs from my head.
Related
Long time reader, first time poster (intimidated in the past)! Hi guys!
So here you go guys, another one who ventured into modding his phone. Seems like following the steps wasn't really going to seal it for me so I'll explain what I did and you tell me what I did wrong.
- Installed Eclipse and Android SDK and fastboot tool on my comp.
- Followed Charrion's guide to one-click rooting my device also using haykuro's root kit
*Followed his steps BUT I actually made a nandroid backup and saved it on my computer.
- Installed the latest cyanogen ROM (from their wiki) on the root of the sdcard and renamed it update.zip
After that, I followed haykuro's guide down to the first commands (after putting the radio and recovery.img on the sdcard from haykuro's give me root)
Used fastboot to input the following comands:
Code:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
Then when I try to reboot into recovery mode, I get stuck on the Rogers screen. I can still access the fastboot and when the device is plugged in through usb it shows fastboot usb on the top left but I just can't access the recovery menu.
Can someone help me? Just getting used to this forum, sorry for not following any procedures. I did read the forum rules and searched the forums. If a thread already exist, I just didn't search well enough.
Thank you
UPDATE:
I use the command prompt to communicate with my Dream in fastboot usb mode and I get the following errors:
C:\Users\Steven>fastboot erase boot
erasing 'boot'... OKAY
C:\Users\Steven>fastboot erase recovery
erasing 'recovery'... OKAY
C:\Users\Steven>fastboot flash recovery recovery.img
error: cannot load 'recovery.img'
I may have a bricked phone! Keeping faith in the hopes that one of you comes and saves me!
New development!
My problem was of course a noob problem! Charrion's post on another thread helped making it clear. My .img were in the same folder as fastboot but I had to specify the entire path for it to work!
Anyways got into the recovery menu and now flashed the latest cyanogen rom to my device but now it's still stuck on the Rogers screen!
Any idea?
To help, here's the info on the fastboot screen:
Dream PVT 32B ENG S-Off
HBOOT-1.33.2005 (DREA21000)
CPLD-4
RADIO-2.22.19.261
There!
Thank you in advance!
I bricked my first phone in January after a month of reading and then following the wrong instructions -- now I am quite hesitant to do things.
On my second phone, I followed the rooting rogers dream full guide at:
[http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod] This worked, although it seemed to have almost as much lag as the rogers rom.
I did a nandroid restore back to my original rogers rom which I had backed up per the instructions in the above guide. This confirmed that I was not seeing much decrease in lag using cyanogenmod.
I want to try going to the 2.22.19.26I radio and use non EBI1 ROMs.
From reading I think I need to use amon-ra recovery with no R on the end.
The radio,recovery and rom should all be non - EBI1.
In my reading, I haven't seen instructions to do what I am looking for.
I have put some commands together below.
Will this work or brick my phone?
It probably is missing some things. For example see step 6.
=============================
1.
start up recovery : Shut down your phone and, while holding the Camera button on the side of the phone, turn it on
again. [Amon_RAs Rogers Dream Recovery (recovery-RA-dream-v1.5.2R.img)]
2.
enter fastboot: press Send to go into fastboot mode.
3.
fastboot devices (to make sure that fastboot "sees" your device)
4.
fastboot flash radio radio.img [from givemeroot.zip]
5.
fastboot erase system -w
6.
is this needed?
fastboot erase boot
7.
fastboot erase recovery
8.
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
9.
fastboot flash system system.img [htc_system_img_14721.zip, stock android 1.6 will get rid of EBI1 kernel patch]
At this point it shoule be a working phone with 2.x radio and stock HTC Android 1.6.
10.
powerdown phone
11.
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Now the phone will be:
Device: Rogers HTC Dream phone
recovery-RA-dream-v1.6.2
Engineering SPL - HBOOT version is 1.33.2005
Radio - 2.22.19.26I
ROM cm-4.2.x
checksums:
givemeroot.zip md5: 4a58a5702fdf899547011888d9cc066f
recovery-RA-dream-v1.6.2.img - MD5Sum: de9a2562ed8b7ef3b8dab4ecf369fd13
htc_system_img_14721.zip (md5sum: 7a3a2a9bc99a0e8894b62eb9921c000d)
=============================
I don't see anything wrong with your instructions and it should work but there are a lot of unnecessary steps. You don't need to wipe your whole phone to change the radio. Just flashing the latest cm update on top will restore the original kernel therefore getting rid of the EBI1 patch.
enter fastboot: press Send to go into fastboot mode.
fastboot flash radio radio.img [from givemeroot.zip]
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Are you with Rogers? Have you signed the waiver yet? Please post back and let us know if Rogers disconnects your data.
beav_35 said:
I don't see anything wrong with your instructions and it should work but there are a lot of unnecessary steps. You don't need to wipe your whole phone to change the radio. Just flashing the latest cm update on top will restore the original kernel therefore getting rid of the EBI1 patch.
enter fastboot: press Send to go into fastboot mode.
fastboot flash radio radio.img [from givemeroot.zip]
fastboot flash recovery recovery-RA-dream-v1.6.2.img [non EBI1 recovery]
boot up to the recovery, and select "Flash zip from sdcard"
Select update-cm-4.2.x.zip and press Home to confirm
Are you with Rogers? Have you signed the waiver yet? Please post back and let us know if Rogers disconnects your data.
Click to expand...
Click to collapse
yea, I did this 2 weeks ago.
I followed this:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
only do it in reverse, as in install the 2.x radio instead and install the ebi0 recovery instead. Then boot into recovery and flash a rom (i would suggest superD rather than cyano because you wont have to also flash the google apps)
troubles...
Thank you for the replies.
I am using this phone on Bell. So the Rogers policy troubles don't come into it.
I checked all the md5sums.
Then I did these commands.
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
oops:
K:\1>c:fastboot flash k:\1\system system.img
sending 'k:\1\system' (58570 KB)... OKAY
writing 'k:\1\system'... FAILED (remote: partition does not exist!)
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
c:fastboot flash system k:\1\system.img
As you can see I typed the command incorrectly for the system image the first time.
Then I issued all the commands again from the beginning -- this time I issued the commands correctly.
When I powered down and then started the phone, it was still stuck on the Rogers logo after 25 minutes. Then I pulled the battery and held camera then power. It did start in the 3 androids screen. Good.
I checked and it also will boot into recovery. Good.
So, now I am not sure what I should do to fix this.
Any ideas?
pictures
Additional info:
pictures of my screens are attached.
david1212 said:
Thank you for the replies.
I am using this phone on Bell. So the Rogers policy troubles don't come into it.
I checked all the md5sums.
Then I did these commands.
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
oops:
K:\1>c:fastboot flash k:\1\system system.img
sending 'k:\1\system' (58570 KB)... OKAY
writing 'k:\1\system'... FAILED (remote: partition does not exist!)
c:fastboot devices
c:fastboot flash radio k:\1\radio.img
c:fastboot erase system -w
c:fastboot erase recovery
c:fastboot flash recovery k:\1\recovery-RA-dream-v1.6.2.img
c:fastboot flash system k:\1\system.img
As you can see I typed the command incorrectly for the system image the first time.
Then I issued all the commands again from the beginning -- this time I issued the commands correctly.
When I powered down and then started the phone, it was still stuck on the Rogers logo after 25 minutes. Then I pulled the battery and held camera then power. It did start in the 3 androids screen. Good.
I checked and it also will boot into recovery. Good.
So, now I am not sure what I should do to fix this.
Any ideas?
Click to expand...
Click to collapse
You for got to flash the base rom or a modified rom. You stopped at the system img so you don't have anythig to boot to. Flash the 1.6 base and you should be good to go.
I don't understand.
I thought that the system.img that I got from the htc_system_img_14721.zip (md5sum: 7a3a2a9bc99a0e8894b62eb9921c000d) is the base android 1.6. I thought this is a full base 1.6 system.
What am I missing?
In recovery just flash the rom you want to use, then it should boot properly.
OK. I applied update-cm-4.2.14.1-signed.zip from recovery and it boots up to CM now.
Thanks.
Great!! Glad you got it working.
BTW There's a newer version of CyanogenMod out.
Yes, newer CM. OK.
Now that I am on the 2.x radio and non-EBI1 recovery, can I use SuperD?
Yes you can use SuperD. Make a nandroid backup, wipe, then flash the update.zip. No need to flash the system.img. There is also a EBI1 port for SuperD so you could have used it before too.
david1212 said:
Yes, newer CM. OK.
Now that I am on the 2.x radio and non-EBI1 recovery, can I use SuperD?
Click to expand...
Click to collapse
you know that you could have used ALL the roms on ebi1 anyway
you just flash a kernel after you flash the rom
It takes literally 2 minutes to make your own kernels with
http://faruq.yandao.com/magicport/
insert rom boot.img (just extract rom to get this), and out comes a kernel !
good news
I am glad I did this.
The phone works better. I don't lose data connection like I did before. The battery life is better.
Now I will make guesses.
The radio works better - has better signal. At my desk, cell reception is not very good. Now the battery is run down less with better connection strength.
My config is now:
-Device: Rogers HTC Dream phone
-Provider: Bell Mobility Canada
-recovery-RA-dream-v1.6.2 [non EBI1]
-spl: 1.33.2005 DREA21000 aka danger spl from rogers_root_unzipme.zip (md5sum: d522e09be7ddec00ef2354533c14cd2f).
-Radio: 2.22.19.26I
-ROM: SuperD 1.9.3 [non EBI1]
questions about downgrading from rogers radio
HI, i'm on a rogers dream using cyan 6.1 and ebi1 kernel. if i downgrade to the 2.22 radio will i have to sign the rogers waiver to get service? i've also heard that the edge network slows down considerably. if there are problems will i be able to go back to the rogers radio?
thanks.
jeremy boyd
Yes, Rogers will disable your data if you don't have the 3.22.26.17 radio unless you sign the waiver. 2.xx is not a downgrade, its a different type of radio. You can always go back to the old radio just make sure your recovery and kernel match your radio.
If you want try this radio. Your phone will be much faster.
http://forum.xda-developers.com/showthread.php?t=831139
I read recently that to flash the danger spl with the least amount of risk it should be done using fastboot. I have fastboot up and running but I am a little confused on using the commands. Can anyone help explain this to me?
You need to boot the phone into the bootloader (spl), open a command prompt on your computer, and cd to where the fastboot binary is.
From here the commands all start with "fastboot." So to erase a partition from the spl, you would enter "fastboot erase recovery" and substitute recovery for whatever you wanna erase. The partitions on the Dream are: system, boot, cache, misc, userdata, and recovery.
To flash a partition you would enter "fastboot flash [partition] [.img file name]"
The .img file has to be in the same folder as the fastboot binary.
Example: "fastboot flash recovery recovery-AmonRa-1.6.2.img"
This is, of course, just about fastboot itself. I have no idea how to flash the spl from fastboot; I didn't even think it could be done. I would suggest using fastboot to flash a custom recovery, and using the recovery partition to flash the spl zip file.
Interesting
Thanks for the reply, that definitely helps me understand fastboot a little more. I was reading in this thread forum.xda-developers.com/showthread.php?t=655097 (sorry no link) that any radio is compatible with any spl as long as you use fastboot to flash the radio and spl, but im having trouble finding any info on how exactly to do it.
Could it possibly be "fastboot flash hboot dangerspl.zip"?
Jaylen said:
Thanks for the reply, that definitely helps me understand fastboot a little more. I was reading in this thread forum.xda-developers.com/showthread.php?t=655097 (sorry no link) that any radio is compatible with any spl as long as you use fastboot to flash the radio and spl, but im having trouble finding any info on how exactly to do it.
Could it possibly be "fastboot flash hboot dangerspl.zip"?
Click to expand...
Click to collapse
You don't flash zip files through fastboot, extract it and flash the .img file directly, but yes, that command is correct.
fastboot flash radio yourfile.img
fastboot flash hboot yourfile.img
then reboot with:
fastboot reboot-bootloader
You'll probably want a recovery .img handy as well, in case you can't get into recovery after flashing. You can flash that with (predictably):
fastboot flash recovery yourfile.img
If anything goes wrong during the radio or hboot flash, DO NOT POWER OFF OR RESTART!! Come back here and get advice. If you reboot the phone without a valid radio or hboot, you will brick.
Remember there's always a risk involved with flashing these sensitive parts of the system.. if you brick it, I was never here
Sweet thanks for helping me understand. One last thing though, I know for sure I have the 2.22.19.26I radio installed already. Should I flash the new 2.22.23.02 radio first then the spl, or the spl and then the new radio?
The new radio is your choice really.. It's not made a lot of difference to me and you shouldn't have any problems just flashing the spl on top of 26i.
Jaylen said:
Sweet thanks for helping me understand. One last thing though, I know for sure I have the 2.22.19.26I radio installed already. Should I flash the new 2.22.23.02 radio first then the spl, or the spl and then the new radio?
Click to expand...
Click to collapse
The order of flashing radio and SPL, in general, is irrelevant. The exception is that the FIRST thing you should ALWAYS flash is an engineering SPL that MATCHES the consumer SPL that you HAVE installed. After that, order makes NO difference. ALWAYS flash radio or spl using FASTBOOT with the exception of the FIRST ENGINEERING SPL (since there IS no fastboot at this point).
Once an engineering SPL is installed, NEVER install a consumer SPL and NEVER use an NBH file.
lbcoder said:
The order of flashing radio and SPL, in general, is irrelevant. The exception is that the FIRST thing you should ALWAYS flash is an engineering SPL that MATCHES the consumer SPL that you HAVE installed. After that, order makes NO difference. ALWAYS flash radio or spl using FASTBOOT with the exception of the FIRST ENGINEERING SPL (since there IS no fastboot at this point).
Once an engineering SPL is installed, NEVER install a consumer SPL and NEVER use an NBH file.
Click to expand...
Click to collapse
Thats what I thought. After reading your thread I flashed the engineering SPL using recovery and now I plan on using fastboot to install the danger SPL. Is it alright to reboot and use recovery to flash a ROM after the SPL is finished or should I just keep using fastboot?
hmmm, just tried to flash with the command "fastboot flash hboot hboot.img" and I got an error, <remote: partition does not exist>. Any ideas?
1) Make sure you have the right radio on your G1.
2) Download the .zip format of the DeathSPL. If you don't have the right radio, download that, too.
3) Boot into recovery mode.
4) If you don't have the right radio on your phone and you had to follow both sentences of step 2, flash the radio.
5) Nandroid backup.
6) Save the Nandroid backup to your computer.
7) WIPE EVERYTHING.
8) Flash the DeathSPL.
9) Boot your phone normally.
10) Reboot your phone into the SPL to make sure that works.
11) Put the Nandroid backup back in the appropriate folder on your card.
12) Flash the Nandroid backup.
blackknightavalon said:
1) Make sure you have the right radio on your G1.
2) Download the .zip format of the DeathSPL. If you don't have the right radio, download that, too.
3) Boot into recovery mode.
4) If you don't have the right radio on your phone and you had to follow both sentences of step 2, flash the radio.
5) Nandroid backup.
6) Save the Nandroid backup to your computer.
7) WIPE EVERYTHING.
8) Flash the DeathSPL.
9) Boot your phone normally.
10) Reboot your phone into the SPL to make sure that works.
11) Put the Nandroid backup back in the appropriate folder on your card.
12) Flash the Nandroid backup.
Click to expand...
Click to collapse
Have you read anything in this thread or any of the awesome work by ezterry over the past few weeks? FLASHING THE SPL THROUGH RECOVERY CAUSED ALL THE BRICKS.
Anyone looking at this thread for help should ignore this and use the fastboot method detailed above.
Jaylen said:
hmmm, just tried to flash with the command "fastboot flash hboot hboot.img" and I got an error, <remote: partition does not exist>. Any ideas?
Click to expand...
Click to collapse
Er.. I've not come across that one before..
Yeah I just put it on hold for the night. It seems that fastboot only flashes to these partitions, system, boot, cache, misc, userdata, and recovery. I'm wondering if the SPL is stored in one of these. I found an ancient JesusFreke thread where he was talking about it being in misc, but I wasn't just gonna go flashing away at random partitions lol...
Ok, I was looking at the commands in fastboot by typing "fastboot ?" in the command prompt and I notice that it says you can flash update.zip files from fastboot. I'm wondering if I rename the original Danger SPL zip file to update.zip and try to flash it this way through fastboot if it will work. Kind of nervous to try it though, what do you guys think?
Yeah that's why I didn't list "hboot" as an available partition. I've had problems with that too. But I've only ever flashed my spl the one time so I didn't even need it.
I would say it's a bad idea to try to flash the spl while in the spl. That may possibly not turn out so nice. I don't know for certain, mind you, but it just sounds dangerous.
FaJu said:
Yeah that's why I didn't list "hboot" as an available partition. I've had problems with that too. But I've only ever flashed my spl the one time so I didn't even need it.
I would say it's a bad idea to try to flash the spl while in the spl. That may possibly not turn out so nice. I don't know for certain, mind you, but it just sounds dangerous.
Click to expand...
Click to collapse
The running spl is in RAM. No need to worry about this.
@Jaylen: That's an interesting one about the partition not being available. I'll look into that -- it could potentially throw a wrench into things.
I don't think its fastboot error or anything, I'm a little bit new at this but I'm pretty sure I set it up correctly. I can see my device in the command prompt, could I have missed a step? @ lbcoder What do you think about flashing the SPL as an update.zip package through fastboot?
Sent from my T-Mobile G1 using the XDA mobile application powered by Tapatalk
hey all, i'm searching around for a general issue i'm having with getting fastboot up and running. i believe i have everything installed, but when i try to run fastboot.exe, it tells me that another file, AdbWinApi.dll, is missing from my comp. but this file is located in another folder in the SDK, platform-tools.... so the file is there and installed, but is there something i need to do with my PATH in my environment variables or something? any help would be amazingly appreciated... i'm trying to get fastboot up and running so i can run some test builds for developers. i'm running 64-bit Windows 7. thx
yogi2010 said:
hey all, i'm searching around for a general issue i'm having with getting fastboot up and running. i believe i have everything installed, but when i try to run fastboot.exe, it tells me that another file, AdbWinApi.dll, is missing from my comp. but this file is located in another folder in the SDK, platform-tools.... so the file is there and installed, but is there something i need to do with my PATH in my environment variables or something? any help would be amazingly appreciated... i'm trying to get fastboot up and running so i can run some test builds for developers. i'm running 64-bit Windows 7. thx
Click to expand...
Click to collapse
You'll need that file to run in ADB mode.
I was trying to improve the speed and battery life on my HTC Dream. I am using cyanogen recovery 1.7.0R. I changed the radio from 2..22.23.02 to 2.22.28.25. I also upgraded the Hboot from 1.33.2005 to 1.33.13d. After making this change the phone hangs at the boot screen and will not enter recovery mode. I am able to get into fastboot however when I try to flash a new recovery, radio or hboot I get signature verify fail. Is there hope for my phone or is it finished?
jmc7895 said:
I was trying to improve the speed and battery life on my HTC Dream. I am using cyanogen recovery 1.7.0R. I changed the radio from 2..22.23.02 to 2.22.28.25. I also upgraded the Hboot from 1.33.2005 to 1.33.13d. After making this change the phone hangs at the boot screen and will not enter recovery mode. I am able to get into fastboot however when I try to flash a new recovery, radio or hboot I get signature verify fail. Is there hope for my phone or is it finished?
Click to expand...
Click to collapse
Most likely you did not flash recovery and your "old" one is corrupted. Your should have read here how to update, but nevertheless because you are able to go into fastboot, now you have to start over.
1. Read the OP of ezTerry's thread carefully
2. Check the type your phone to identify the nbh-file you have to flash to recover from your current situation (most likely you will need the orange-xxx.nbh)
3. Flash that nbh file using fastboot
Now you have an engineering SPL and you can flash recovery, radio and the 1.33.0013d SPL again.
AndDiSa said:
Most likely you did not flash recovery and your "old" one is corrupted. Your should have read here how to update, but nevertheless because you are able to go into fastboot, now you have to start over.
1. Read the OP of ezTerry's thread carefully
2. Check the type your phone to identify the nbh-file you have to flash to recover from your current situation (most likely you will need the orange-xxx.nbh)
3. Flash that nbh file using fastboot
Now you have an engineering SPL and you can flash recovery, radio and the 1.33.0013d SPL again.
Click to expand...
Click to collapse
Thank you for your help. I followed the link and was able to use the orange.nbh to get the phone to boot then used fastboot to reload a recovery image. Thanks again.
Bricked. Red "Your device is corrupt. It can't be trusted and may not work properly"
Following this guide I ended up bricking my Nexus 6. Please ask questions as this is my first time rooting a device.
http://forum.xda-developers.com/showpost.php?p=56938530&postcount=1
After typing "fastboot reboot" my phone begun rebooting, stopped and went to the red "Your device is corrupt. It can't be trusted and may not work properly". Now I am able to get to the fastboot menu. I am also able to get to the android recovery menu. Can anyone point me in the direction to get my phone working again?
Thank you in advance
You can get into fastboot. So restore to stock image. Or since you have custom recovery restore your working backup.
Then read the thread on root. Not just the first post. Read the most recent ones... They are the ones with the most up to date info. Never flash stuff or follow guides with out reading like the last 3-4 pages of the thread as well as the full OP AT A MINIMUM.
1)download google factory image
2)Extract everything in one folder.
3)Delete userdata.img from folder(because once i left it in folder and started flashing images one by one and ended up with empty internal storage.lost everything)
4)use these commands to flash
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
fastboot flash boot C:/image-shamu-XXXXXX/boot.img
fastboot flash recovery C:/image-shamu-XXXXXX/recovery.img
fastboot erase cache
5)reboot
You don't have to delete userdata.img... Just dont flash it, and don't use flashall
Your manually typing these commands. Just don't type it. Understand what the partitions are and don't flash the ones you don't want.
And on that point, rather then flash the stock recovery, flash something like TWRP since your trying to root.
Wow. Thank you guys. I really appreciate it. Great group here.
Got it back up and running with 6.0.1 with your help. Since I have gotten this far I think I'll try out some ROM's.
Thanks again.