Database Develop

[Q] Common Telnetd problem? - unable to root

Common Telnetd problem - unable to root
What's up xda!! This is my first post ever!
..please be kind.
I am experiencing a n00b issue w/ rooting my G1. So far I have been able to get up to where I am on RC29 and <enter>reboot<enter> successfully reboots my phone! This is great up until I'm told to hit the enter key twice, type "telnetd" and press enter. after the phone starts up.
FOOD FOR THOUGHT:
I believe I have ADB drivers installed properly installed
I am able to run Droid Explorer and it connects and recognizes my unit
I also have the following files on my SD CARD prepared
recovery-RA-dream-v1.5.2
update.zip
I have also read that ONE solution is to look for someone with an current T-Mobile Monthly Account and ask to borrow their sim card so I can install the Telnetd and enable WiFi past the Google Login(I have asked a fellow and I was told an aggressive NO, apparently people are afriad of anything related to hacking and their SIM CARDS)
I have the G1 Original SPL currently
Also when booting into recovery Alt+L gives me the Log that shows ""
I hope to have made an appropriate first post granted I've been searching for answers and help and am still experiencing issues. I look forward to participating in this forum in the future looks like you guys have been having fun for a while!
Any suggestions are definitely welcome.

Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.

RE: Maybe try to update your phone to Android 1.6
raven_raven said:
Maybe try to update your phone to Android 1.6 with official OTA packages (last 3 ones are which you should flash) by stock recovery (it will accept this packages if you apply them in correct order - every package is named sth like "CRB43 to CRC1" - then you which should be applied) and then try one-click root app? When you have superuser priviliges you can download ROM Manager and flash custom recovery, then by recovery flash engeenering SPL. And with this SPL you can do what you want with your G1.
I rooted my G1 both ways with goldcard and with one-click root and I have to say, one click-root ROX.
Click to expand...
Click to collapse
Hey raven, thanks for the reply!
By doing this update are you suggesting that I use the G1 Original SPL to flash the Offical Dream RC29 ROM (OTA_ROM RC) listed on that page, IF so what should follow that? Would I be allowed to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC) and the Official RC33 Update - from RC30 to RC33 (OTA_ROM RC) with the same update.zip that came from the G1 Original SPL also?!
I'm lost with your suggestion, b/c if it requires me to enable WiFi to get the OTA update I would still be unable get pass the Google login. Would I not be stuck back to where I am now? As of right now, I am at the Android Welcome Screen with the G1 Original SPL and RC29 that were not listed on that page AND so far unable to get root b/c of unavailability of TelnetD and WiFi. I will proudly follow those instructions?? Sounds like following the flash of Offical Dream RC29 ROM (OTA_ROM RC), that I would need to somehow use a method to flash the Official RC30 Patch - from RC29 to RC30 (Removed Root) (OTA_ROM RC)...I think?!

Excitement!!!!!
EXCITEMENT!!!!!
I used:::::
1- Plug your G1 & Install Drivers.
2- Without Sim Card in Your G1, <enter>setprop persist.service.adb.enable 1<enter> Even though u dont see what u typing, but u are actually executing a Command on your G1 to Enable USB Debugging in Settings.
3- Once u Execute that Command USB Drivers will be Installed again, but this time will be recognised as ADB Interface.
4- Click Start>Run>cmd> to Command Prompt
5- Type c:\adb devices (If your Device is Connected u will see it)
6- Restart your G1 but now With Sim, to see the Activation Screen then Plug USB Cable & Type c:\adb devices (to make sure u are connected)
7- Type c:\adb shell (U will see a $ sign) Just Copy & Paste this into Command Prompt (am start -a android.intent.action.MAIN -n com.android.settings/.Settings) The Settings Screen will Appear, now Switch on Wi-Fi & Connect to the Internet.
8- Now u can either Login with your Existing or Create New Account with Google.
Click to expand...
Click to collapse
here is where I was lost, I'm sure many are running into the same issue. The adb.exe that is located on my PC is what the command prompt should be finding, however there are other folder possibilities in where the application is ran to even use the adb functions. For instance, my adb.exe was installed in "c:\android-sdk-windows\tools" instead of strictly on the "c:\" I was not aware that I would be controlling the phone unit through my command prompt as well!! silly me, something so easy can become one of the biggest problems. ONE MONTH LATER!!!! THANKS XDA!

[GUIDE] Turkeys' Ultimate Guide to Root Wildfire v42.1.2 (Easy & Safe!)

Turkeys' ULTIMATE Guide to Rooting v42.1.2
Note: It does not work on 2.2.1 Wildfire's (i.e. - Any bought after Feb - March 2011)
Like this guide? Hit the thanks button at the bottom left of this post
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me, you can do so below.
GBP
EUR
USD

So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...

So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...

Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF

Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!

A2SD
Note: It has come to my attention that doing this with ROM Manager doesn't work most of the time. If you have problems please partition your card another way. (I recommend GParted - There is a Live CD if you don't have Linux)
First, we need to partition your SD card with ROM Manager. This will wipe all the data on your SD card so please backup before continuing.
1) Open ROM Manager (Download it from the Market if you don't have it - Although you will need the Market Mod to show all apps) and press Menu > Manually Override Recovery **Not sure exactly what it says, pls could someone help me out here** Then scroll down to Partition SD Card. Choose the ext size you want for your apps to be installed on, then tap 0 for swap size, then tap OK to reboot into recovery and start partitioning!
Note: While it's partitioning it will show a picture of an Android. You can press (Power?) to see what it's actually doing and if there's any errors.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.

Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Buzz. Now, you need to recall what version of Android you were on before you rooted. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.

Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse

Reserved for good measure.

I'm sure this will help many people. Should be sticky'd

HCDR.Jacob said:
I'm sure this will help many people. Should be sticky'd
Click to expand...
Click to collapse
Good Idea!!!
For the rru you need to click on the windows mobile section and select buzz NOT bravo

Added A2SD guides, misc fix & unroot guide. Bump to v42.1.2

Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin

PanGalactic said:
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
Click to expand...
Click to collapse
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now

42turkeys said:
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
Click to expand...
Click to collapse
And buzz is under windows mobile for some reason

The guide really great....but the shipped rom website don't have RUU for Buzz

coltrain said:
The guide really great....but the shipped rom website don't have RUU for Buzz
Click to expand...
Click to collapse
Look under windows mobile - who put it there? Those files do work.

This thread still not stickied?

Piece of art already. Should be stickied for sure.

I thought a bit about 'reporting' the thread to make a mod notice it but it said specifically what report was to be used for , so i didn't do it , i guess we'll have to bump it up so it gets stickied. Great post !!

[GUIDE] [froyo] Downgrade to 1.36

How to downgrade to 1.36 (release ruu)
This only works on froyo based roms, gingerbread radio won't downgrade
About:
Currently it is not necessary to downgrade since no exploits have been found. But for the case we have to downgrade, we have it. It is currently only tested on the leaked ASIA rom, but cannot imagine it is not working on later/other ROMs.
I have nothing to do with this method, i only wrote the guide.
This guide is based on the DHD downgrade (so many similarities will be found)
Anyhow keep in mind that:
You will lose all data on your phone (not from your sd-card)
First boot after downgrade can take pretty long (a few minutes) so dont be scared it didn't work and absolutly DON'T pull your battery out. Just wait a while, if its beyond 15min and still not working. Come here and ask. And DONT PULL THE BATTERY unless you are told to.
Thanks:
Scotty2, rhcp and Guhl for development of this method
jkoljo for putting up the DHD guide
bippolinno for the ruu mirror
lge73 for testing and getting it done
If i miss someone, please tell me and i add u
System requirements:
HTC Sync (or ADB drivers)
Incredible S with build number higher than 1.36
A working ADB setup (ADB is included in the downgrade package though)
Howto downgrade:
If you have a branded device, Goldcard is required (have not tested it if its required for a non-branded device EDIT: unbranded seems to work without goldcard)
The PG32IMG.zip (if the download is not working extract it from the RUU, can be done by yourself (see below))
Connect Incredible S to a computer. Charge only, USB Debugging enabled!
Open up cmd/terminal and go to downgrade folder
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
If you got "#" in the result, you have temproot! Proceed:
Code:
cd /data/local/tmp
./misc_version -s 1.31.405.1
Put the PG32IMG.zip on the root of your SD Card (trough adb push or just connect it as a disk drive)
Reboot into bootloader (adb reboot-bootloader or hold volume down while rebooting)
Follow the instructions
Ready, you have downgraded your Incredible S to release ROM
Extracting rom.zip from RUU.exe
Ruu can be found here
Make sure your INC s is connected
Start installer
Click next
Click next
Goto your temp folder (open the start menu, type %tmp% and press enter, ty l0st.prophet)
Sort folders on date
Pick the most recend and look inside one of that folders for rom.zip
Copy it to downgrade folder (or anywhere else) and rename to PG32IMG.zip
Disclaimer:
I am not responsible for bricks

Thanks to all involved!
I would recommend that you mention all data on the device will be wiped by this downgrade and that the reboot after downgrade will take a little while and not to get scared or do silly things like pull the battery out!

Thank you for this very clear guide !
Now, I just need to know where to get the European rom ! (i will install the european rom instead of the asian)
Someone can give me the link ? Please ?

It is in the guide (RUU.exe). Just download and install. Just received message from the tester that it is also possible with just the misc_version hack and use the RUU.exe
It is the oldest currently available. But i'm not 100% sure if its the same as the old European Rom, but it has the same number as mine (Netherlands) so i quite sure its the same.

I can not extract with ruu...
Cause i have an asian version. I didn't upgraded it...
I just need to install the european Rom.
If someone can share this for me, it will be great !
Thank you guys

Like i said: download the ruu from this topic it is the european. Than follow the guide. I don't know how I can be any clearer.
Don't know what the problem is since all you say that you want the European ROM. Btw if you have preinstalled Asian ROM, there is a possibility that there are minor differences. But you can always flash the Asian ROM back.

Thank you again...
Sorry but my English and android's knowledge are not so good

That's no problem. I advice to get a little basic knowledge about Android, since this process on the IS is still in its early stage a lot can go wrong and currently there are not many methods available for fixing it. Not that a lot can go wrong here, but if it does you are screwed.
So if you don't know what is going on, I advice to stay at the default stock ROM.

Extracting rom.zip from RUU.exe
Ruu can be found here
Make sure your INC s is connected
Start installer
Click next
Click next
Goto your temp folder
Sort folders on date
Pick the most recend and look inside one of that folders for rom.zip
Copy it to downgrade folder (or anywhere else) and rename to PG32IMG.zip
Oh hell 2 nights I used to figure it out were that temp folder could be.
First I had to turn on the option see hidden files.
C:/Users/%user%/Appdata/Local/Temp
Windows is so frustrating wen your used to a Mac.

ab65 said:
Extracting rom.zip from RUU.exe
Ruu can be found here
Make sure your INC s is connected
Start installer
Click next
Click next
Goto your temp folder
Sort folders on date
Pick the most recend and look inside one of that folders for rom.zip
Copy it to downgrade folder (or anywhere else) and rename to PG32IMG.zip
Oh hell 2 nights I used to figure it out were that temp folder could be.
First I had to turn on the option see hidden files.
C:/Users/%user%/Appdata/Local/Temp
Windows is so frustrating wen your used to a Mac.
Click to expand...
Click to collapse
It's alot simpler than that, just open the start menu, type %tmp% and press enter. Voila!

thanks l0st.prophet
that information comes in handy. it's so easy if you know
don't ask how long I used to get a working ADB setup, and that is also a piece of cake wen you figured it out.
( I'm still on PPC Mac and muss use the Pc of my son, and he is enjoying it seeing me so helpless on windows system)
But it's a great tutorial and in the end all went fine.
Thank you xda comunity.

thanks for share

this is very helpful

does this work for s-on devices?

shiftyllama said:
does this work for s-on devices?
Click to expand...
Click to collapse
Yes, although it's untested on the new GB ROMs.

I get an error when running the adb command:
adb shell /data/local/tmp/psneuter
reading:
Failed to set prot mask <Inappropriate ioctl for device>
I'm trying to downgrade from Vivo_Gingerbread_S_Virgin_Mobile_AU_2.12.981.2
Any ideas. Does the psneuter exploit no longer work with gingerbread?

doctorsax said:
Yes, although it's untested on the new GB ROMs.
Click to expand...
Click to collapse
Tested on Gingerbread 2.3.3 but, the radio will not downgrade so the OS does not load.
The "How to" is a little different tho.
Note: Do not update to GB if you want to downgrade back to froyo anytime soon.
I'll attach this here for safe keeping.

touchpro247 said:
Tested on Gingerbread 2.3.3 but, the radio will not downgrade so the OS does not load.
The "How to" is a little different tho.
Note: Do not update to GB if you want to downgrade back to froyo anytime soon.
I'll attach this here for safe keeping.
Click to expand...
Click to collapse
so am i stuck with the aussie virgin ROM untill an RUU for europe is released?

shiftyllama said:
so am i stuck with the aussie virgin ROM untill an RUU for europe is released?
Click to expand...
Click to collapse
Yes or until a full root method is released.
I am trying to downgrade now tho and then force the ota.
Wish me luck...

touchpro247 said:
Yes or until a full root method is released.
I am trying to downgrade now tho and then force the ota.
Wish me luck...
Click to expand...
Click to collapse
good luck.....
and let us know if you manage it and how!!

Lenovo Ideapad K1 One-Click Root (Mostly)

First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.

digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.

gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.

question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.

jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.

Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?

the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??

Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?

READ THE POST
IDEApad not THINKpad. no it wont work.

First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.

I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?

taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's

Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.

This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50

Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50

I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD

I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk

Anyone have the root? Megaupload is down forever.

[Q] Where to copy superSU zipfile

Hi all,
I am trying to root an HTC One; I'm following the instruction at htconeroot.com.
For some reason, I am getting stuck at the stage at which I am supposed to install CWM SuperSU.
I have the Android app QuickSSHD installed on my phone.
Using scp on my Linux laptop (Linux Mint 16), I transfer the SuperSU zip file to the phone, copying it to /sdcard/.
If I browse the phone using ES FIle Manager app, I can verify the zip file is there, along with the various other subdirectories under /sdcard/
However, when I reboot and go to the bootloader, click on Install, and then go to /sdcard/, I see nothing. No zipfile, no subdirs. I am wondering whether /sdcard/ is in fact mounted; it would seem not.
I have tried copying the SuperSU zipfile to the root directory of the phone, but that isn't possible; I don't seem to have write permissions.
From the instructions:
Sign in through the setup process then copy the CWM-SuperSU-v1.30.zip file in HTCOneRoot folder to anywhere on your HTC One’s internal storage.
Click to expand...
Click to collapse
However, it isn't clear to me precisely how I am supposed to do this -- or where it should go.
Am I missing something here?

cbrace said:
Hi all,
I am trying to root an HTC One; I'm following the instruction at htconeroot.com.
For some reason, I am getting stuck at the stage at which I am supposed to install CWM SuperSU.
I have the Android app QuickSSHD installed on my phone.
Using scp on my Linux laptop (Linux Mint 16), I transfer the SuperSU zip file to the phone, copying it to /sdcard/.
If I browse the phone using ES FIle Manager app, I can verify the zip file is there, along with the various other subdirectories under /sdcard/
However, when I reboot and go to the bootloader, click on Install, and then go to /sdcard/, I see nothing. No zipfile, no subdirs. I am wondering whether /sdcard/ is in fact mounted; it would seem not.
I have tried copying the SuperSU zipfile to the root directory of the phone, but that isn't possible; I don't seem to have write permissions.
From the instructions: However, it isn't clear to me precisely how I am supposed to do this -- or where it should go.
Am I missing something here?
Click to expand...
Click to collapse
Are you S-Off and unlocked? If that's the case, I believe there's a flashable zip (and instructional videos) in the TWRP thread. If you're not S-Off and unlocked yet, you'll want to look here:
http://firewater-soff.com/instructions/
You'll use the "temp root" method, but I believe you'll still have to be on 4.3 for it to work.
Sent from my HTC6500LVW using Tapatalk

feedback
cbrace said:
Hi all,
I am trying to root an HTC One; I'm following the instruction at htconeroot.com.
For some reason, I am getting stuck at the stage at which I am supposed to install CWM SuperSU.
I have the Android app QuickSSHD installed on my phone.
Using scp on my Linux laptop (Linux Mint 16), I transfer the SuperSU zip file to the phone, copying it to /sdcard/.
If I browse the phone using ES FIle Manager app, I can verify the zip file is there, along with the various other subdirectories under /sdcard/
However, when I reboot and go to the bootloader, click on Install, and then go to /sdcard/, I see nothing. No zipfile, no subdirs. I am wondering whether /sdcard/ is in fact mounted; it would seem not.
I have tried copying the SuperSU zipfile to the root directory of the phone, but that isn't possible; I don't seem to have write permissions.
From the instructions: However, it isn't clear to me precisely how I am supposed to do this -- or where it should go.
Am I missing something here?
Click to expand...
Click to collapse
Try moving the zip to /sdcard/0/ see if that helps at all...Let me know, thx lj

Moved to the HTC One Q&A (out of verizon) at the request of OP.

Thanks for moving this thread to the right place. Now, just to confirm: I have an HTC ONE which is unlocked; I bought it without a plan.
Try moving the zip to /sdcard/0/ see if that helps at all
Click to expand...
Click to collapse
I see that sub-directory on my Nexus tablet, so I know what you are referring to, but I don't see it on the ONE.
If you're not S-Off and unlocked yet, you'll want to look here:
Click to expand...
Click to collapse
Thanks, I am just getting up to speed here with the terminology. I've unlocked the booloader, but the phone is still S-ON.I'll try to get that sorted out now.

OK, I have used revone to set S-OFF
I have also installed, or at least run temproot.Yes, I see the # prompt.
But when I reboot and go into TWRP, it still can't see anything in /sdcard
It also says that the device does not appear to rooted.
Any thoughts on how best to move forward here?
I would like to be able to:
Install Kitkat
Deinstall some HTC cruft
Thanks

cbrace said:
OK, I have used revone to set S-OFF
I have also installed, or at least run temproot.Yes, I see the # prompt.
But when I reboot and go into TWRP, it still can't see anything in /sdcard
It also says that the device does not appear to rooted.
Any thoughts on how best to move forward here?
I would like to be able to:
Install Kitkat
Deinstall some HTC cruft
Thanks
Click to expand...
Click to collapse
If you do have a Verizon phone you would have better luck their.
But I'll try .. whats your fastboot getvar all results (minus your serial no and IEMI). What version of recovery are you using ?

cbrace said:
OK, I have used revone to set S-OFF
I have also installed, or at least run temproot.Yes, I see the # prompt.
But when I reboot and go into TWRP, it still can't see anything in /sdcard
It also says that the device does not appear to rooted.
Any thoughts on how best to move forward here?
I would like to be able to:
Install Kitkat
Deinstall some HTC cruft
Thanks
Click to expand...
Click to collapse
So your PC can see your device in fastboot??? and your S-off and unlocked bootloader???
What is your end game do you want to be on the new stock 4.4.2 rooted or are you going to a Custom Rom???

lj50036 said:
What is your end game do you want to be on the new stock 4.4.2 rooted or are you going to a Custom Rom???
Click to expand...
Click to collapse
I'd be happy with the stock 4.4

feedback
cbrace said:
I'd be happy with the stock 4.4
Click to expand...
Click to collapse
Well as long as you can get to fastboot and your PC can see the phone and you are S-off and unlocked head over to this forum and read up... There will be a firmware update and than a rom flash... Just do your reading there is a lot of info but santod has done a very nice job....
http://forum.xda-developers.com/showthread.php?t=2485319
---------- Post added at 09:46 AM ---------- Previous post was at 09:43 AM ----------
Just ask either here or there if you have any questions. I will be more than happy to help you get there....