Hi all, I am going to be as thorough as I can. I am rather new, and I'm stuck trying to downgrade my MT4G to froyo (PD15IMG). I have read the tutorials, and learned enough about adb to attempt this task, but I think by doing the HTC Bootloader unlocking update last week, it may be the reason I'm stuck. I follow the instructions on the tutorial, to gain temp root, until I get to the part where I should get a "#" in the command Window when I type "adb shell" but I keep getting "$" instead, although everything seems to be going ok until I get to that point.
*Also, I put the PD15IMG.zip on the root of my sd card, and start my phone in bootloader mode, and it finds the PD15IMG.zip, and a blue progress bar appears in the top right corner of my phone for about 90 seconds, it then displays "parsing PD15IMG.zip" then stops at the hboot screen and does nothing. I just select power down, then power on my phone and nothing will have been done to my phone. I guess what I need to know is, by doing the HTC bootloader unlock update (which I did before I read that it was a bad idea), can I still downgrade and root with normal methods, or will I have to do something different?
Sent from my HTC Glacier using Tapatalk
You can start differently. Since you've unlocked the bootloader, try to flash recovery directly, by downloading recovery image directly from Clockworkmod site, rebooting to FASTBOOT (adb reboot bootloader) and using the command "fastboot flash recovery your_just_downloaded_recovery.img".
If recovery flash doesn't work for you - download the 2.2.1 PD15IMG, unzip it, and flash the following 2 files from it:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase userdata
Then reboot. You should end up on 2.2.1, which is perm-rootable using the guide (Visionary for temp-root, gfree for S-OFF, and then perm-root if you want).
Then flash the recovery and the engineering bootloader.
Here is what I did, I am giving a link to pastebin as instructed, it seems to go perfectly until I try to flash the StockRom. In the meantime I will attempt what was just posted above^^^^^^^ http://pastebin.com/fYrC6tAZ
One last thing before i have to throw away my phone. I couldnt leave well enough alone. I did this "fastboot flash boot boot.img" as you stated in the post above. It was successful. I then entered this one "fastboot flash system system.img", and it failed (said the img was too big or something) so I did the "fastboot-windows reboot" command and it is now stuck on the white HTC MyTouch 4g splashscreen. Is my phone toast? My PC no longer recognizes that my phone is connected to the USB port, however I can hold the volume dwn & power button and it comes on in the hboot mode.Is there any hope?
Also, when I boot it up by vol/dwn & pwr, the Hboot screen comes up and finds the PD15IMG that is on my sd card, goes through a 1 minute or so process (a blue status bar loads in top right corner), then it just stays on the hboot. It did that before it stuck on the splash screen, but never actually wrote anything i dont beleive.
OK its letting me use FASTBOOT and here is exactly what I got when i tried to flash the 2nd file in your post above. It came from the PD15IMG.zip as you instructed:
C:\adb>fastboot flash system system.img
sending 'system' (571388 KB)... FAILED (remote: data length is too large)
finished. total time: 0.016s
Can someone please let me know if there is hope for my phone? I can communicate with it through Fastboot (on my PC) and it will boot up in hboot mode. But it WON'T go past the Tmobile/MyTouch splash screen. If I get it fixed, I promise to never touch it again until I study! I truly feel there is hope, but I think don't know enough to figure it out. I loaded the PD15IMG on my SD, and it attempts to flash it, (a blue status bar appears in top right corner and fills up in about 90 seconds), but afterwards, it still sticks on splashscreen. Is there anything I can do to fix it? Anything I can flash it with in Fastboot? Please anyone?
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Jack_R1 said:
You mixed 2 ways, and did it completely wrong way. And you didn't attempt to flash the recovery at all.
The first part, that went well (till ./flashgc), already prepared your phone for downgrading, and you should have recognized and understood it. You don't need anything else, no flashes from bootloader or anything. All you needed was to continue - put PD15IMG.ZIP on the SD card, reboot into bootloader, and let it downgrade.
You can still do it, so please do.
---------- Post added at 06:16 PM ---------- Previous post was at 06:13 PM ----------
Once you end up on 2.2.1, please follow the "Ultimate rooting guide" from Development section, and flash Engineering bootloader.
Click to expand...
Click to collapse
Thank for your response. I have tried doing the PD15IMG.zip by booting my phone in bootloader mode. It finds the PD15IMG.zip and then a blue progress bar appears in the top right corner of the phone, finishes in about 90 seconds, the a message appears that says "wrong zip file". I would be happy just to get my phone back on with the gingerbread 2.3.4 on it, and simply leave it alone until I know what Im doing. Is there a way to just flash the original s/w back on it? If so if you could tell me how I will not mess with it again until I study alot more. But flashing the PD15IMG doesnt appear to be working for me.
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Jack_R1 said:
Download the file again, and check MD5SUM on it before you use it.
If it responds "wrong ZIP" - it's because the ZIP is corrupted. When you'll download a good ZIP, it'll work.
Click to expand...
Click to collapse
Ok you were right, the one I had the wrong MD5SUM, but i d/l the correct one, it had the correct MD5SUM, but it still gave me the "wrong zip file error". I feel like there is hope, but I cant figure this out!! Thank you for trying, is there anything else I can do? I also tried going into recovery and doing factory reset/ data wipe etc...but it continues to get stuck on the splash screen....
How did you copy the correct one to the phone's SD card, and where did you put it? You either didn't copy it to your SD card, or named it wrong, or put it in wrong location, not overwriting the older file.
In any case, if flashing PD15IMG fails for you:
Download CWM recovery from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-glacier.img
Boot to bootloader.
Enter FASTBOOT.
Execute:
fastboot flash recovery recovery-clockwork-5.0.2.0-glacier.img
Boot to recovery. You should have Clockworkmod.
Download a stock rooted 2.2.1 ROM from Development section.
Flash it in Clockworkmod recovery.
Extract boot.img from this ROM.
Flash it in fastboot, using "fastboot flash boot boot.img".
Boot into the ROM.
Proceed with gfree.
OK!! I got it fixed and it all makes sense to me now! I flashed the 2.2.1 boot.img to my phone, when it still had the 2.3.4 on it. It was as simple as that. I hadnt flashed the downgrade on it when I flashed the boot.img and I guess it was a mismatch. I read your last post to extract the "boot.img" from the rom and then it clicked! Yesterday I wrote the 2.2.1 boot img. to a phone that had 2.3.4...so I found a stock 2.3.4 rom, extracted the boot.img from it a BAM! its rolling again....thank you so much....
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Jack_R1 said:
Yes, indeed, you flashed a mismatched, older kernel to your ROM. I was suggesting that you install custom recovery and change the ROM to match your boot.img, but the other way around also works - as long as you don't need to root your phone, that is.
Click to expand...
Click to collapse
Well I will soon attempt it again, however I think I need to read a little more so I can understand the concept of what I am doing. I learned a ton by making that mistake. But as soo as I got it fixed, I couldnt resist, I used revovery and flashed [ROM]:: ProjectMIUI 2.2.17 [R6]- UPDATED 2/21/12 - [Stable + Smooth from the DEV section and I have never been happier with my phones performance! I will soon try the cyanmod, but I want to chill with this rom for a week or so. Again, I appreciate your help, I learned alot.
As long as you don't mind flashing kernels separately using fastboot for each ROM you flash, you can go indefinitely and flash ROMs as much as you like with your current setup, not needing anything else. The only good reason for you to go for S-OFF would be to flash Engineering HBOOT, to be able to flash kernels from recovery directly, avoiding extra fastboot step.
Also, thanks for finally confirming that you can flash recovery using fastboot on HTC-Dev-unlocked device. There was one device that didn't allow it (I think Incredible S, but not sure), so it's good to know that on MT4G it works as it should.
Related
[ I'll send 10$ via Paypal to the person who can get me running on Cyanogen ]
Right, so I'm trying to install CyanogenMod on my Rogers HTC Dream. I've managed to get to SPL 1.33.2005.
I'm following this guide:
http://forum.xda-developers.com/showthread.php?t=544654
I've extracted both image files to the root of my SD card from the "givemeroot.zip" which are "radio.img" and "recovery.img" but am at a loss on how I should proceed from here. Specifically, the following statement:
"IMPORTANT: make sure you have the rom you'd like to install in the root of your sd card as update.zip (YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE UPDATE.ZIP TO GET ONE)"
Is CyanogenMod considered a "rom", or am I confused? I have CM's zip file on my desktop as "update-cm-4.2.5-signed.zip" - does that mean I need to simply rename it to "update.zip"? Any help here would be graciously welcome!
Cheers!
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
This is the guide I followed and was much easier to follow.
fattyl said:
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
This is the guide I followed and was much easier to follow.
Click to expand...
Click to collapse
That tutorial still confuses me and constantly loops you back to other articles, which in turn do the same. I'm still not where what exactly I'm expected to do at this stage.
[EDIT] I should clarify. I'm not sure what "if" applies to me in point 5. I've installed the 1.33.2005 CPL but do not believe the phone is rooted.
Ah crap, did see that you weren't rooted, sorry, but I haven't rooted in a long time and cant help you with rooting, sorry, but after you get rooted, if you have RA's recovery or Cyanogen's recovery, you can pick "Apply sdcard: Choose zip", if not, just rename update-cm-4.2.5-signed.zip to update.zip and flash it as normal using "Apply sdcard: update.zip"
Hope this helps.
Rogers, heres your root
haykuro said:
---
hyeprofile requested i link to his rooting for dummies guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
---
edit: almost forgot to include the gr33tz! D:
this hack brought to you by dream_kill, and myself.
---
edit: for those of you that don't know how to get to SPL 1.33.2005 i recommend reading here: http://forum.xda-developers.com/showthread.php?t=532224 (under Rooting Rogers).
---
(note: this is for the dream, the method works for the magic you just need to flash a magic compatible recovery.img)
This requires that you use SPL 1.33.2005. (this is safe on all rogers dream devices.)
so if you don't have that already, go get it here.
once you are at SPL 1.33.2005 (AND ONLY THEN)
download this
(md5: 4a58a5702fdf899547011888d9cc066f .. sha1: 99e38e4f8798e952e67421a42e7b053ea70957b7)
extract both images wherever you'd like.
IMPORTANT: make sure you have the rom you'd like to install in the root of your sd card as update.zip (YOU WILL NOT HAVE A ROM INSTALLED AFTER YOU COMPLETE THE FOLLOWING STEPS, YOU WILL HAVE TO USE THE UPDATE.ZIP TO GET ONE)
boot into spl and fastboot (power off, hold camera button, power on, press the back arrow to get into "fastboot" mode)
type in the following:
Code:
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery.img
POWER OFF (not reboot, power it off) THE DEVICE. (you can do this using the corresponding button [it says it on the screen] or just pull the battery [make sure everything is done flashing of course])
(if you don't boot into recovery or accidentally rebooted, just pull the battery [if you notice top left it should read "FASTBOOT" or "FASTBOOT USB" if it's plugged in] you're not bricked, you just need to access recovery, not standard boot ;P)
now hold down the HOME button and power it on, you should boot into recovery mode now, go ahead and ALT+S to flash your rom, and enjoy! now you can flash anything you see in the forums
EDIT:
So i noticed people were talking about reverting back (not sure why you'd want to )
Regardless, heres the original radio (3.22.20.17) and the original recovery (WARNING: UNROOTED) from rogers dream:
http://www.stevebirstok.com/android/losemyroot.zip
Code:
fastboot flash radio rogersradio.img
fastboot flash recovery rogersrecovery.img
fastboot erase system -w
and flash the update.zip found somewhere on this forum ;P
EDIT 2:
as far as this ram / memory loss goes:
C:\Users\haykuro\Desktop>sha1sum radiog1.img radioion.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radiog1.img
14163559b04ba8c9daead5e34465ebf5bafa7bd1 *radioion.img
radiog1.img is the radio.img i provide in the givemeroot.zip, radioion.img is straight off here there are no specific radios between 32A and 32B boards, so that isn't why you're losing memory. i'm trying to figure it out, so if anyones willing to do some testing and post results, please do so.
Click to expand...
Click to collapse
Once you do that:
1. Upgrade your recovery image to the latest Amon-RA(Link in my sig)
2. Use it to partition your sdcard w/ a FAT32, 512MB ext3 and 96MB linux-swap(backup anything you want first)
3. Put on the latest CM(flash the HTC rom and then the CM ROM as per instructions in the CM thread)
I also recommend you get the latest radio and SPL...if they're the same for rogers as they are on the G1, links in my sig. Not absolutely necessary, but nice to have so you can run any ROM you want.
has anyone tried this guide? http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Rogers_Dream_EBI1_to_CyanogenMod
apparently it is supposed to take me from stock rogers to cyanmod rooted i got all the way to the end where in my cmd i type erase system -w that works but when i type the next command flash system system.img it says cannot load system.img..... has anyone used this guide and can offer help? ive gone over all the steps over and over im certain i havnt missed anything
You can try verifying the checksum that is posted on the HTC download page or you could just try downloading it again in case something is corrupt.
You could also try flashing an update.zip that doesn't contain the radio. I think someone posted one a while back on the forum. Also I think if you would just skip that step your phone would still work but you would just be missing the google apps like maps. This is better than no phone for now and you can try to get it to work later.
Hello,
I updated my UK Xoom 3G (MZ601) via OTA to 3.2 (H.6.5-17-3) last year.
Since I got interested in rooting the device I read I have to install CWM first.
However, when going into recovery mode (for testing) all I get is a green android bot.
Thanks to some googling I found some website that mentions to hold the power button (while the green android bot is shown) and press volume up, then release the power key. Now I see the stock 3e recovery menu.
Is it safe to simply unlock the bootloader and flash CWM via ADB? Or am I required to flash back to the xoom dev stock rom because of the green fella? My question refers to this part:
Or, if you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
(This Wipes your Xoom )
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Not sure why I would have to do that? In the end, I'd want to have a rooted stock 3.2.
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Then, you back into recovery, and push the new cwm recovery using adb
(look on the xda xoom's section: you'll find the right tutorial; should start with downloading adb, downloading cwm into the same directory as where you put the adb drivers for the xoom. Then open command as administrator, etc.)
After that, you should have CWM (or I recommend the touch Rogue recovery! ) on your Xoom, instead of the ugly little green bot, now allowing you to flash many, many ROMs, zips and many other to your device!
Enjoy. Hope this is clear enough and helps you towards the right direction! (if so, please do thank me, since I only just made an XDA account and would like at least one thanked post lol.
If not, please PM me or ask further explanations in this thread! )
adelancker said:
First unlock it indeed while seeing the green bot in recovery.
(using the commands you posted yourself)
Click to expand...
Click to collapse
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Landorin said:
I suppose you only refer to the adb commands without flashing the img files, right?
I still don't know why that other thread suggested to flash back to an older version first (see quote in my first posting)? Can anyone tell me if I have to downgrade at all?
Click to expand...
Click to collapse
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
---------- Post added at 01:23 PM ---------- Previous post was at 01:05 PM ----------
adelancker said:
First unlock it using those fastboot commands you posted. You should in this series of commands not flash anything yet. Just unlock it first. When rebooting and showing the Moto logo:
Get back into recovery and then push the new recovery.img using adb commands
As far as I know, there is not one reason to downgrade. Should work just fine.
Click to expand...
Click to collapse
Otherwise, use this as your guideline and you should be fine:
http://forum.xda-developers.com/showthread.php?t=1249798
Thank you! All worked out fine. I followed the guide step by step, I did not downgrade the existing ROM.
In case someone else gets into the same situation and wonders how to do it:
once everything is set up for ADB and the device is found (command adb devices) type this in your command prompt window:
Code:
adb reboot bootloader
waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot oem unlock
Confirmed the warning. Then had the device booting up normally to re-enable USB debugging. Then continued:
Code:
adb reboot bootloader
again waited for fastboot protocol text to show up on Xoom device, then:
Code:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
When it said flashing done I restarted the Xoom (holding power button + volume up). About 3-4 sec after seeing the Motorola pic I hit volume down ("android recovery" is displayed), then volume up and CWM showed up.
Since I was already in CWM I also applied the universal root method ("install zip from sdcard" -> "choose zip from sdcard", then selected the actual file on the sd card, installed it, rebooted). Root works.
P.S.: just realized silly me forgot to do a nanddump before rooting.
something like forgetting a nanddump only happens once!
Glad to see it worked for you!
Even happier to see you didn't need to downgrade.
Once you flash a custom ROM, you'll have 3G and ICS!
I did the same a couple of months ago, and my device felt brand new!
I rooted through cyanogenmod method, then unrooted (went back to stock 2.2.1) with the stock P15100.zip. I had another hardware issue with my phone (microphone failing) and thought it could be software. The mic was still broken and I wanted to root again so went through cyanogen method again flashing CWM. I was able to reboot once into recovery to flash synth's ICS. When I try to fully reboot, then reboot into recovery again, I got bootloop for a minute, then eventually booted into the rom. I tried flashing 4ext and same issue. I tried flashing CWM again from app and still have the issue. I'm just guessing recovery is corrupted and it needs to be formatted and re-flashed? Anyone know how to format recovery via adb and then push cwm or 4ext?
Any help much is appreciated.
You can flash a recovery through terminal emulator. As I recall, the commands are:
su
flash_image recovery recoveryname.img
Sounds like you might be having bigger issues, though. I hope your recovery partition isn't going kaput.
Jack_R1 might have an idea.
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Nicgraner said:
Man, Jack_R1 is still around these parts? But as for OP, definitely sounds like your recovery is corrupt. What you want to do is if you have any fastboot/ADB knowledge is you're going to want to download the recovery.img of your choice, name it "recovery.img" then place it in your ADB folder, plug your phone in in Fastboot mode and then type in the following commands:
Code:
Fastboot devices
it should show you a number followed by "fastboot" after this type
Code:
fastboot delete recovery
it should spew out how long it took followed by "recovery deleted" or something like that.
lastly you're going to flash the recovery that you downloaded. Type
Code:
fastboot flash recovery recovery.img
That should do it! PM me if you need any other help
Click to expand...
Click to collapse
I have used adb a bit (for root with cyanogen method). I'm guessing that the delete command will reformat the recovery partition? I'll give this a go when I get home and get back to ya. Thanks for the reply! Is there a way to download the 4ext recovery img file?
Edit:
I downloaded the CWM touch img and connected to the phone in fastboot. Was able to follow your instructions, but the command is erase not delete. When I put in the delete command it came up with the instructions and was able to figure it out. Flashed recovery and I can now boot into recovery every time from fastboot, terminal, adb, and from power prompt in rom! BOOYAH! Thanks a ton!
Jack_R1 said:
Yes, I still visit here
OP, what phone do you have? You're writing a wrong name for PD15IMG.
In any case, if you indeed have PD15IMG - find "root for S-OFF users" thread in Development, get the PD15IMG with CWM from there, flash it just like you flashed return-to-stock package, and boot into recovery. If it doesn't work - it means that it's not the recovery that's corrupted.
And I suspect that you're just not understanding correctly what your phone does, and/or not actually booting into recovery.
Click to expand...
Click to collapse
Hey Jack,
I have HTC Glacier. Was a typo for the PD15IMG name. I think I have a decent understanding of the phone, and most likely have a corrupted recovery partition. Seems that instead of just flashing a recovery over a recovery, I may need to reformat the partition and then flash? I'll try flashing the file you suggest and report back. If it is not the recovery that is corrupted, what else could be the issue? Possibly an issue with the bootloader not allowing the phone to boot into recovery? Thanks for the reply.
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Jack_R1 said:
Flashing recovery isn't copying a file. When you flash IMG through bootloader, it is flashed just like what it is - a complete image. Formatting the partition doesn't do anything, since it has no "format" - the image flashed by the bootloader contains both the structure and the data, just like a CD/DVD image does, for example.
The possible options I can think of are:
1) Your recovery partition is physically bad - unlikely.
2) Your bootloader is corrupted - could possibly lead to you being unable to enter recovery.
3) Something that prevents your phone from entering recovery - i.e. a stuck button or something - or you're doing it wrong. I'm afraid that what you're describing as "phone bootloops for a minute and then boots a ROM" isn't really a bootloop - because these phones can't get out of bootloop on their own, if booting failed once - it'll fail always. Logcat can confirm this. I believe it's just the ROM that's booting normally when you try to enter recovery, so, in this case, since you didn't specify how exactly you're trying to enter recovery - it seems like you're either doing it wrong, or when you try to enter recovery you're not getting there.
To help people help you, please write down the exact way you're using when trying to enter recovery, and if you know more than one way - try them all (from bootloader, by adb reboot recovery, directly booting without flashing by "fastboot boot", etc). And post your HBOOT version.
Click to expand...
Click to collapse
Sorry if I wasn't more descriptive. I really appreciate your help and everything you have done for this community. Seems the recovery was corrupted by the 4ext app. I was able to extract the recovery.img from the 4ext download and was able to flash it via fastboot. Everything boots properly now. HBoot is 0.85.2007 FYI. Thanks again!
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
ZyreHD said:
The title may sound strange but it's true.
I have this phone for just one week and haven't used it to call (reason: moving from T-Mobile to Tele2, this takes time. Date: 25e).
Rooting will allow me to do some stuff like a different boot animation which caught my attention. What I just don't want to happen is that I brick my phone to the point that it doesn't work anymore. Secondly I void my warranty which is something I don't feel so good about seeing I just got the phone.
I don't know this yet but if I root is. Can I back up everything from the phone? Contacts, Apps, settings etc etc? So when something goes wrong I can install a image of my back up?
Sadly I am pretty dark now. It's all new and while I would like to give it a shot, some things don't feel right for me just yet as stuff is unclear to me on how do it it.
Can XDA help me maybe? Also what are some really cool ROM's? I wanted to get Touchwiz but there is no (lol) and Cyanogenmod is like Stock Android so it seems ...pointless?
Best regards,
Robert Oortwijn
Click to expand...
Click to collapse
setup adb and learn how to flash back to stock in fastboot. you will never brick your device beyond repair as long as you are capable of following directions for flashing and rooting and such
Here's the sticky from the other forum.
That is very useful and they talk in layman's terms. When I first got my N4, I followed this and got custom everything following the instruction posted there.
I'm no expert, but I rooted my N4 in the first week very easily, and as long as you follow all the instructions in the XDA thread then you won't go wrong. If you are really worried then you can use a toolkit as that will automate everything, but I'd never recommend that as you aren't really learning.
As for backing everything up, you can back up some things like your contacts, WiFi passwords and so on to your Google account. Apps is a lot harder if you want the data, but I believe an ABD backup will work - again, look at the appropriate thread (or use the toolkit for backing up).
And Roms, most of them have a stock feel with more features such as extra customization, but if you want a different look you can use themes - you can get touchwiz themes on the play store for ROMs like CM.
Sent from my Nexus 4 using xda premium
you dont need root to flash roms or kernels, you need a custom recovery(and an unlocked bootloader). you need root to run root apps and to mess around with the root file system.
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
username8611 said:
I agree with tom about the toolkits. There is a large correlation between people who use toolkits and people who break their phone and have no idea what they are doing. Learning fastboot will save you from huge headaches and regret in the future.
Click to expand...
Click to collapse
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
ZyreHD said:
Finally got it rooted and installing CM10.1 went easy!
What I only want to know now is:
How do I relock the phone from rooted to unrooted again? Same for bootloader.
Removal of Clockwork.
And remove CM10.1 and get stock android back.
Thats all!
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/showthread.php?t=2010312 well, it will show you exactly how to get back to stock if need be.
We were all scared and nervous too when we first rooted an android device. Lol. When you get it done you soon realize how easy it was. :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Can someone help? So I have Cyanogenmod installed on the phone and got USB debug on. When i unplug and go into the bootloader and then plug the micro-usb in my PC doesn't detect the phone. I do have the drivers installed.
It did work, now it doesn't meaning I can't perform the stuff needed.
ps: If your wondering if I use the SDK to put everything to stock well sorry but I can't get the SDK to work. Java issues and errors. Pain in the ass so I stop with that.
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Edit 2: 5min later and still at the X logo. It does move but nothing. Is my phone dead?
ZyreHD said:
In the bootloader and then recovery I get a Android logo with a red /!\ ?
Edit 1: I tried a reboot and now it doesn't hang. The X logo is moving but nothing yet.
Click to expand...
Click to collapse
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
im not sure if i reading it right, but from what i can gather, you flashed cm10.1, then found out adb doesnt work right so you are ditching it and going back to stock? i wouldnt worry about it too much. as long as you can still use fastboot in the bootloader, thats all you need to do anything to save yourself from certain death. adb is more helpful for gathering up data if you cant lose it before flashing back to stock
username8611 said:
if you are getting and android with a red "!", it sounds like you didnt flash a custom recovery. you need to be on either cwm, or twrp.
edit: it sounds like something got jacked and you need to start over again. it sounds like you are going back to stock, right?
start from the bootloader with fastboot. format/erase all the partitions and reflash everything and you should be golden
Click to expand...
Click to collapse
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Edit 3:
Retrying in the meantime. Now at writing system (done)
Edit 4:
Now I'm at the point where it's erasing userdata....
Edit 5: couple of minutes later and still going.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Click to expand...
Click to collapse
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to the bootloader. type this in fastboot, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
username8611 said:
unplug anything that is plugged into your phone. make sure it is completely turned off. hold volume down and power until it vibrates. it should take you straight to the bootloader
---------- Post added at 02:21 PM ---------- Previous post was at 02:16 PM ----------
yeah something is amiss, hold on let me type this up real quick
go here and download OCCAM factory image. open up the file you downloaded and you should see userdata.img, system.img, etc.... take all the files that end in img and move them to your directory for fastboot aka: /platform-tools, or whatever you use for fastboot.
boot your phone to fastboot. type this, pressing enter after each line:
fastboot format userdata
fastboot format system
fastboot format cache
fastboot erase boot
fastboot erase recovery
fastboot reboot-bootloader
now for the flashing,
fastboot flash recovery recovery.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot-bootloader
fastboot flash userdata userdata.img
OPTIONAL... if you think your radio is messed up -----> fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot
voila
Click to expand...
Click to collapse
I got a different option now. format userdata and I get options. Flash all, erase, update filename etc.
ZyreHD said:
For some reason. I pressed the buttons to get into the bootloader I get this:
Download Mode. Do not unplug?
Edit: I'm back in the bootloader. I didn't press the combination right sending me into Download Mode.
Edit 2:
So what I did was this. I followed these instruction on how to install custom ROMS: http://www.androidrootz.com/2013/02/how-to-install-custom-roms-on-nexus-4.html I also followed them in the procedure of rooting your phone.
I tried it out and now wanted to go back to stock. So I found a article also by them and did that: http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
When I was at the point where the cmd said: erasing use rdata the article said: 5min, but it took longer so I unplugged the USB.
Now I'm here where I can't boot the OS anymore. Bootloader does work but recovery doesn't as I get the /!\
Click to expand...
Click to collapse
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
El Daddy said:
When you see the android laying down that is stock recovery. Press volume up and power to open the menu. Then you can factory reset.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I only have 4 options there.
Reboot system now
apply update from ADB
wipe data/factory reset....
Oh I got it. It formatted and I rebooted. For now it only shows the X logo. Will go downstairs in the meantime to get something to drink. It might take some time maybe?
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
nevermind, you were talking about the options in recovery
ZyreHD said:
THANKS YOU SO MUCH!!!
Just as I wanted to go it booted!!!!!!!!!!!!!!!!! 2 hours of hard search and it was this small thing to do? I was really afraid that I had wiped the factory reset of the phone!!!!
Thank you again, all of those who helped!!!!:laugh::laugh::good::highfive:
Click to expand...
Click to collapse
Congrats. That's why I wrote what I did in your other thread. Read, read, read. Its better to know how to fix things before they happen then frantically trying to find out how fix them while they happen.
Sent from my Nexus 7 using xda premium
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
Theres a hardware method to boot into the bootloader, this i think you can test, just to see if you can at least get into bootloader.....nothing more
Details in the official nvidia link
http://nv-tegra.nvidia.com/gitweb/?...ob_plain;f=README_SHIELD;hb=rel-22r18-partner
There's a thread here on the "questions" thread with users reporting that the timing of the hardware method can be a pain in the you know where.............might be worth looking into that thread for their experiences in booting the bootloader using the hardware method
Disclaimer:If your brave enough to risk a brick, read on
I suspect this might be the 2.1 stock/twrp issue........current twrp, or current stock dont play nice
Its a good sign that SOMETHINGS loading, rather then NOTHING booting, but dont know if theirs a solution
My analysis of the situation, of what little i know, the -w (wipe) command was expecting a stock recovery but instead got twrp, which is why your in this situation.........maybe, i stress maybe, if you could reflash stock again, you might be able to boot into android stock again and try full android again, leaving out twrp, until a twrp fix is found
Edit
Saying that, if the bootloader is, as i suspect, now using twrp to flash things, then you might be boned....... im no expert on bootloaders, stock "recoveries" and how they work, so i might be wrong on that
Reports around here say that 1.3 stock firmware is the recommended back to stock firmware, apparently, flashing any other firmware versions, bring their own issues.............
From 1.3 stock, use nvidias official OTA to upgrade from 1.3 stock, to 2.1 stock, then try 2.1 full android again...........note, i dont think you can skip firmwares i.e. you have to upgrade to 1.4, then to 2.0, then to 2.1, alot of downloading.......the OTA does'nt give you any other choice
Before doing anything that ive suggested, wait till someone with more experience to come along........i dont want to be responsible for you fully bricking your shield..........just wanna give you an idea of what i think has happened
If worse comes to worse, if you have warrenty, get a replacement
Gd luck........remember, this is an analysis of your predicament of what i THINK might of happened, and what steps, i likely might of entertained.......after looking into it more thouroughly, knowing that i could get a replacement if it went downhill.........so your mileage might vary
Edits
Crappy grammer, further musings, clarifications
Thanks.[/QUOTE]
puppinoo said:
Well,
basically subject says all.
I tried to install zulu99 Full android rom 2.1.
basically 'fastboot flash system system.img worked' but 'fastboot -w' failed ('no space left' error).
So I rebooted hoping to reflash a nandroid backup but now the box keeps on rebooting into twrp trying to wipe cache and data but failing. after a while it stops and black screen appears.
I attach the screen it presents when reboots.
Please tell me I didn't trash 220 euros.
Thanks.
Click to expand...
Click to collapse
I had something similar about... shield goes booting in recovery and trying delete some cache and keeps repeat and repeat
Hardware boot in fastboot / bootloader mode
Accessing Bootloader via Hardware
Unplug power from the Shield Android TV. *
Wait a few seconds.
Hold down the power button.
Plug in power
Count to three
Release the power button
You should see the bootloader screen.
If you hold it down too long or not long enough, it simply doesn’t work.
Restore Shield Android TV to Stock
P.s. Personally me I followed this instructions and kind of magically got it in bootloader mode. First done by instruction and then just gave up and pressed randomly and fastboot screen appear. Thanks God I had to done only once, if I would do again I wouldn't had patients
Good luck with this, hope you will get sorted
Here will be link about where I got instructions about hardware boot
http://nvidiashieldzone.com/index.php/shield-android-tv/root-shield-android-tv/
Sent from my Nokia 3310 using free xda app
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
EDIT with joy : I followed all the steps using that rom and it seems everything worked. I reconfiguring the box now. Thanks for help.
basically the procedure I intend to follow is this part (please confirm it's ok):
To flash this recovery image to your SHIELD, run the following commands from
the directory where you extracted the recovery image package. If this is the
first time you have done this procedure, you must unlock the bootloader. Get
DTB file name to use for flashing for your product(see below):
P.s. maybe Since past fastboot commands failed and I only flashed system from zulu99 I could skip the 'fastboot flash boot boot.img' command so if it fails again I still can attempt the fastboot process again?
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
fastboot flash dtb <DTB file name>
puppinoo said:
Thanks a lot fro your help.
I was able to put the box in fastboot mode.
Since I'm not that expert can you tell me where and which rom I have to download (I have a french 16gb version of the box).
Then I'd need to know exactly what commands to performs (even a link to a tutorial is fine).
I really appreciate your help. It seems I can (hopefully) save the box.
EDIT: The fastboot command gave me a (not enough space) when I bricked the box. Is there a risk it could happen again while flashing stock? No idea how much space I have left on the box really.
EDIT2: I found this page: https://developer.nvidia.com/shield-open-source
and I'm downloading this rom called nv-recovery-image-shield-atv-upgrade2_1.zip
and Intend to follow these instructions: http://developer.download.nvidia.co...TV/Upgrade-2.1/HowTo-Flash-Recovery-Image.txt
Can anyone please confirm I'm doing right?
Click to expand...
Click to collapse
You are on the right way with those links
P.s. You can do manual one by one entering or paste and copy those commands or (I'm doing) drag and drop file "flash-all.bat" on cmd previous opened there where you have abd/fastboot etc files and extracted RIGHT FIRMWARE (like shift and right click mouse "open command prompt here"
And after this all sit down and relax
Anyway you are on the right way.
P.s. Hope you download adb fastboot drivers somewhere from Internet !?!
Sent from my Nokia 3310 using free xda app