Database Users

I need help please... messed up loaded ROMs

Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!

do a search for adb for dummies on this site. it should help

Buck Shot said:
Basically I unlocked bootloader and tried to load ROM. I tried the Desire and Cynagen. I was not successful at either. I manage to do a factory reset and the phone is working, except my wi-fi is shot, and when i recieve the initial OTA update it starts to download and then stops and I get the triangle of death as I call it with the lil android guy. I realy dont know what the hell Im doing and I need inch by inch restoring ROM for dummies instruction. I would like to go back to stock.I have been in threads but i get lost on certain things. I dont know what a adb is or how to acess it. I did read the noobies guide.. Please help as I am ready to chuck this thing out the window, i love my N1
I have searched the ORIGINAL SHIPPING TUTORIAL
and one other thread but i guess i cant post links.
please help!!!
Click to expand...
Click to collapse
did you try to load rom in the recovery img? This also happened to me (triangle with the android guy) and I thought I couldnt flash custom roms. For some reason the regular reboot to recovery mode gives me the triangle of death as you call it.
I got around this by loading in into bootloader mode then going to my command console, getting to my skd tools folder, and then typing
fastboot boot (whatever recovery img you used)
Then everything worked perfectly.

They are going to move this to General....
You did not follow the steps correctly it sounds.
Did you Load Amon Ras Recovery?
IF YES,
GO into Recovery
WIPE data
Flash Cyanogen's Latest ROM
Flash Google Apps available on Cyanogen's front page Post
In future ALWAYS nandroid Backup...
If you did not load Amon Ra's Recovery, you should go do this from fastboot.

I'll try to explain it to you:
1. The Bootloader is unlocked (you see the open lock at the first screen)? If you don't see the lock this is the first you should do or send it directly in for repair!
2. Then you have to flash the Recovery ROM (http://forum.xda-developers.com/showthread.php?t=611829) This you need to flash an update.zip Exact instalation guide is in the Link.
3. The ROM. If you want Stock then here you'll find it as an update.zip: http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
Choose one without includet Radio ROM!!! (See below why!)
4. Copy the ROM to your SD Card Root
5. Go into Recovery ROM (Vol Down with Power and then select recovery with the Volume button). There you select wipe and choose the first entry there (wipe data and cache)
6. Stay in Recovery ROM and selct Flash from update.zip and select the update.zip. Wait until everything is done and you are promted to reset your N1.
(DON'T MESS AROUND WITH THE RADIO ROM IF YOU DON'T KNOW EXACTLY WHAT YOU ARE DOING. DON'T UNDERSTAND ME WRONG, I THINK YOU HAVE NO GLIMPS WHAT YOU ARE DOING SO BETTER LEAVE THE RADIO ROM ALONE!!! YOU MAY BRICK (DESTROY) YOUR PHONE WITH IT!!! If you dont believe: http://android.modaco.com/content/g...odaco-com/303716/nexus-cannot-on-after-flash/)
7. There should be no 7. Everything should be fine by now.
Hope I could help.
** 100 Posts **

Stheoft u are my hero!!! Now hold do I get the multitouch update? lol sorry
DID YOU EVERY KNOW THAT UR MY HERRRRRRROOOOO
edit: i got it, im back to square one... thanks alot for all ur help

@ Buck Shot, this is a development forum... threads with question shud go in the general forum... these are making the development forum a mess....

Anyone Willing to Help? Stock To FroYo

I guess I missed this over the weekend and I am looking for the original install that I dont need to have root for. I have been reading over the threads here and in the Dev forum and I am not seeing any links to the download for Non-Root users.
I am to much of a ***** to root my phone. i spent way to much cash on it and i am too worried something will go wrong.
So here is want I am asing for
A. The original non root install with instructions on how to do it
or
B. Someone to help walk me through the process of rooting and getting FroYo 2.2 set up on my phone.
Please shoot me a PM if your willing to help out. I am just way to worried if I do this without someone who knows what they are doing I am going to screw up my phone, and my wife would never let me buy another one ...lol
Can somsone help out a fellow Dev, thanks

Sorry I can't post links but here you go
androidandme.com/2010/05/news/how-to-manually-install-android-2-2-on-your-nexus-one/

Ya just found it buried in a thread
Thanks
See if I would have spent another 10 minutes searching I would have found it without having to ask ...lol
Got to remember to scan threads for 30 minutes not 20 before asking ...lol

Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)

Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.

Paul22000 said:
Or use this: http://forum.xda-developers.com/showthread.php?p=6043779#post6043779
(Or the Root/2.2 links in my sig.)
Click to expand...
Click to collapse
Paul, is that Avatar a picture of YOU?

OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol

attn1 said:
Paul, is that Avatar a picture of YOU?
Click to expand...
Click to collapse
All I wil say is:
λ

LOL ...........

you don't need to root to install froyo and you don't need to hook up your nexus to a pc. my method is pretty simple and it works.
edit: I shouldn't say it's my method. Its actully a backdoor to installing froyo.

theletterj said:
Okay, I'll give you the general idea, as I understand it:
The FRF50 ROM that was leaked from Google is exclusively for ERE27 Builds only. Unless that is the native build on your phone, you will not be able to apply that as is.
Paul O'Brien, over at Modaco, repacked it so that it can be flashed with any current ROMs. Though he's said that there are no conditions, there in fact are a few stipulations to be aware of.
-If you have never unlocked your bootloader, you won't be able to flash anything at all. Something to think about. There's a few threads here dedicated to this topic alone. It voids your warranty so that is why some people are holding off and waiting for the official OTA update to be released.
-Though it's true that you don't have to be rooted to flash Paul's repack, unless you have ERE27 stock, you need to flash using one of the custom recovery images. And in order to flash your recovery.img, you need to be rooted. So you need to have had rooted before.
So the steps, from stock, would be:
(1) Unlock your bootloader, via flashboot.
(2) Flash superuser to your boot.img (aka rooting)
(3) Flash a custom recovery to recovery.img (I use RA)
(4) Flash Paul's FRF50 repack using said recovery image.
I'm sorry I can't post the links to the relavant posts, but my status as a member doesn't allow me to. Hope this helped clear some things up for you.
Click to expand...
Click to collapse
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a nandroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader by flashing the Google Froyo Release with the stock recovery:
Google Froyo Release
You must be on release ERE27 for this to work.
Here's a link to some instructions on how to use the stock recovery program:
jp_macaroni's thread
I suspect that since most people have already rooted or cannot get to ERE27, Paul's guide is the best way to go for them.
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.

jcohenlv said:
OMG theres a search feature!!!
Really OMG I didnt know this!
I guess me saying I searched threads and the site for 20 minutes was something you missed.
But thanks to all who actually decided to help and not be another one of these "USE SEARCH" people.
I respect the work you do for us here Paul, but come on man. Read before making a post like that ....lol
Click to expand...
Click to collapse
Yeah you know, everyone is new once. It's easy to sort out the tripe from the real deal when you've been around the block once or twice. Paul is doing his best to be helpful and not cause more confusion.
The problem isn't that people can't search so much as it is that searches yield too much conflicting information, so lets not jump down people's throats when they ask for a point of clarification. Instead, lets start asking moderators to sticky good info and pulling redundant/bad info so that searches are more meaningful. The number of new threads in here because of the Froyo release is mind numbingly high. Let's all try to exercise some patience.

attn1 said:
Okay, there's a lot of good info out there mixed in with a lot of mis-information.
Your steps will work BUT:
I prefer to do it this way:
Unlock the boot loader via fastboot
Flash Amon_RA 170 recovery for Nexus One
Do a Nadroid Backup
Flash your ROM of choice (Modaco's FROYO in this case)
If you are running stock recovery, you CAN flash, but only Google's updates. If you have a T-mobile N1 this may work for you without unlocking the bootloader:
If you are running a custom recovery, you can flash custom updates, but NOT Google's updates intended for any stock phone/firmware level.
You don't need to root (root access) to the current ROM before flashing a custom ROM. You only need to unlock the bootloader and install a custom recovery image.
Click to expand...
Click to collapse
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.

theletterj said:
I'm not disagreeing with you, but as far as I know, yes, you do have to root in order to flash Amon_RA Recovery to your phone. If that's not correct, I apologize for spreading misinformation.
Click to expand...
Click to collapse
You only need to unlock the bootloader. You do not need root.
Unlocking the boot loader allows installation of an alternate recovery, which allows you to install custom software to the existing ROM or to install a custom ROM. It's updating the ROM that allows you to gain root access, not unlocking the boot loader. It goes in this order:
> Unlock boot loader (void warranty - still not rooted)
> Install custom recovery
> nandroid backup (recommended/optional)
> Update ROM (for root access - or not)

The original instructions worked perfect
All that was needed was to change the name to update.zip load it on the root of the SD card then but the phone in bootloader and load recovery from SD.
Took about 5 minutes.
Once the phone came up it did a few things and took about another 5 minutes to chill on the processes then I was able to use the phone without any problems.
So for those interested here are the exact steps:
This is for NON Rooted T-Mobile Version!!!!
To manually install Android 2.2 on the Nexus One, perform the following steps:
1. Download the official Android 2.2 firmware for the Nexus One.
2. Copy the file to your microSD card and name it update.zip (newb warning: not update.zip.zip)
3. Power off your phone.
4. Hold down the VOLUME DOWN button and power it back on.
5. The phone will now search for files like PB00IMG.zip, etc. This is normal. Scroll down to recovery (using Volume Down Key) and press the POWER button.
6. When you see the “/!\” symbol, press the POWER button and the Volume Up button at the same time. You should be presented with a menu and one of the options should be “Apply sdcard:update.zip”.
7. Use the trackball to navigate to “apply sdcard:update.zip” and select it.
8. When you see “Install from sdcard complete”, select “reboot system now”.
Wait 5 minutes, phone will reboot once rebooted let the phone sit for about 5 minutes then you are good to go. It couldn't be any easier

Trying to root - problems [SOLVED]

Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.

Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.

So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?

I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.

Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App

whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.

Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?

Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.

i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique

Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.

Did you run the stage1 and stage2 bats while in recovery?

dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?

jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.

Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?

Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?

Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave

Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App

EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?

Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.

jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!

[Beta] Custom ROM (system.img) without unlocked bootloader!!!

FIRST TRY... Edited system.img (KERNEL 2.6.36.3 only!!!)
WARNING: ONLY USE THIS IF YOU HAVE A BACKUP OF YOUR /DEV/BLOCK/MMCBLK0P3 IF YOU DONT HAVE ONE YET, MAKE ONE BY USING THIS:​
IF FROM ADB:
ADB SHELL
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
IF FROM TERMINAL EMULATOR:
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
THIS IS A FUNCTIONAL FILE SYSTEM, I AM WORKING ON A CUSTOM ROM WITHOUT HAVING TO HAVE THE BOOTLOADER UNLOCKED.
THE ONLY THING THAT HAS CHANGED ON THIS SYSTEM.IMG IS THE BOOT ANIMATION (INSTEAD OF "ANDROID" IT HAS THE HONEYCOMB BEE) AND THE FONT HAS CHANGED ALSO...
AGAIN, THIS IS JUST A TEST, IT IS THE FULL FILE SYSTEM TO BE USED ON A DAILY BASIS BUT DOES NOT HAVE ANY OPTIMIZED FILES AT THIS TIME.
Alright, now that you have read the warning... download this file here:
LINK = http://www.megaupload.com/?d=1YZSDVZI = LINK
You can then push the file through ADB by typing:
dd if=/sdcard/blk0p3_sys.img of=/dev/block/mmcblk0p3
Post if it worked for you or if it did not, this will help me troubleshoot...
PLEASE MAKE SURE THAT YOU MAKE A BACKUP OF YOUR FILES FIRST!!! THIS FILE IS BASED ON USA MODEL 1.104.05_GEN1 ACER A500. I RECOMMEND TO TRY ONLY IF YOU HAVE HAD TO UNBRICK YOUR TABLET BEFORE. I DONT WANT TO MESS UP YOUR TABLET!!! YOU HAVE BEEN WARNED!!! JEJEJE
Please post if it has worked for you or if it glitched, I am currently in trial and error so... my tablet gets bricked 1-3 times a day because I am testing different things on the system images... hopefully, I can find a way to have root on the image or at least include:
1. File manager
2. ROOT or at least the Gingerbreak.apk already installed.
3. Terminal emulator
4. Custom background upon boot
As stated, it works for me but I have only 1 tablet so if you are daring enough, please dont hessitate to help me in getting this up and running...
I AM NOT A DEVELOPER SO PLEASE BARE WITH ME AS I AM TRYING TO LEARN AS I GO... JEJEJE

props to you!
u crazy.

I don't see any attachment or link...

Euclid's Brother said:
I don't see any attachment or link...
Click to expand...
Click to collapse
Sorry about that, i've updated the post... jejeje

Beta Rom
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.

tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
THANKS!!! this is what I am needing... at this time, there is NOTHING ELSE that has been changed on the file system... I am just testing making sure that my changes stick... I am hoping to be able to change some more things... As long as its working... I will continue changing things ... Until I can get an image that is worthy of "Custom ROM" status... jejeje

tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
Did you fix your issue if you haven't I'm on gtalk if you want help I pulled my hair out for 2.5 days before I fixed it
Sent from my A500 using XDA Premium App

cant figure out how to multiquote as clicking the buttons dont do anything.
but just look at "Crsdr37"'s post in general with the imgs and update zip to get back to stock and updates!!!
and to the person who made the IMG keep up the good work. im not gonna flash it and im happy with being stock and getting updates now ;D

Have you figured out how to apply the incremental updates to the img?
I suspect it's just replacing files, I'll look at it when I get to a PC.

Ive been away from my tablet today. I put the post up and went out tonight... jejeje
Thank you guys that tested my image... if it worked for you, THANKS!!! if ou didnt, then let me know what did not work...
THIS IS NOT NOT NOT AN UPDATED IMAGE, IF YOU CHECK THE DESCRIPTION, THIS IS A TEST IMAGE TO GET A CUSTOM ROM OVER TO THE ACER A500... I AM TESTING SO I WILL NOT ANSWER QUESTIONS ABOUT UPDATES... THAT IS FOR MY OTHER POST... SORRY PEOPLE.

Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.

i am going to try it as well nice thing you guys do

Great
Cheers man, !

So, pulling your system image from /DEV/BLOCK/MMCBLK0P3, then modifying it, then pushing it back works?
Let me try and understand here:
I thought the whole locked bootloader thing checked signatures on the images that are about to be loaded into memory, such as the image in /system.
According to this:
http://www.reddit.com/r/Android/comments/hkbf3/so_you_want_to_know_about_bootloaders_heres_the/
It says:
What does a bootloader do with digital signatures?
It uses them to check any update that passes through it.
So: dd any partition we want to modify, back it up in a safe place, mount the img we get from that, make changes within the img, and dd it back, = all good?
ie: signed bootloaders only have to do with installing update.zips on the sdcard?
Can someone clear this up for me?
Thanks!

Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express

If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.

netham45 said:
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
Click to expand...
Click to collapse
Dude, chill man... You are right, your question does ask about headway for the updates but here are the facts:
You are asking about updates on a BETA Rom that is just in testing...
I took your question to be if the ROM file had the updates (My fault for sure). I was not yelling per say nor trying to be rude but rather making sure that people are aware this is in no way an updated image and should not be treated as such... THIS IS A TEST ROM and since your question was posted within its thread, I took it as if it was directed to the image itself and not toward me and my development...
Look, as stated, im not a developer man, this stuff is a little hard for me to do. I do apologize because I did not answer your question correctly/completely but as far as the comment... Its what I meant. jejeje

tomlogan1 said:
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
Click to expand...
Click to collapse
Have restored to complete US stock. Had a lot of problems related to SD cards, had to swap them out to avoid errors on the actual update.zip file, but am back to normal. Now if I can just keep my hands off until the 3.1 update comes out, or there is custom ROM...

mapaz04 said:
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Click to expand...
Click to collapse
That's what I've doing for a while now....I guess I should have shared xD
been installing custom fonts and trying to change some of the system settings from other customized roms directly from the tablet.
Instead of reflashing wouldn't it be easier to just provide the files to push into the tablet? just my 0.02

Yeah, I can provide files for you guys to install but what I was going for was an image that contained everything already setup so you can just flash it over ur old one allowing the "customization" to appear upon install/pushin the file... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express

[Q] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this

wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day

You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?

If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?

Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?

okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.

Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .

okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now

I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?