Related
A friend of mine had her Eris metroflashed to MetroPCS. Calls and SMS work, but she wants me to provision the rest of it to work like i did with my own Eris on metro. I tried it to find out the Eris one click root app is not on the market anymore however i had the APK, erisone.apk. I loaded it to her SD card and downloaded Astro File Manager and attempted to install, which it proceeded to tell me it couldnt be installed on that phone. All i need is RA-Eris recovery as i will be loading a custom ROM. Is there an easy way to change the recovery on it so i can do this? I was thinking i just needed to update to 2.1 OTA (can someone provide the link? the old link from google doesnt work anymore) then the Erisone.apk will work (this apk loads custom recovery as well as a root very easily). I need to load a custom ROM before i can begin with the provisioning, what do you guys think i should do?
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
roirraW "edor" ehT said:
Does this work http://forum.xda-developers.com/showthread.php?t=742228?
Or see this list of options that scary alien provided http://forum.xda-developers.com/showthread.php?p=10013596#post10013596.
Click to expand...
Click to collapse
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Helgaiden said:
The top one is one i tried. The bottom link there mainly concerns rooting. Im trying to install a custom rom thats already rooted so i don't care much for rooting but i guess its necessary to install a new recovery image right? All i want to do is install ra-eris recovery so i can load a custom rom. The one click method you linked automatically installs a new recovery image and thats what im really after. I just don't think that one you linked is compatible with 1.5
Click to expand...
Click to collapse
You have to be rooted and have a custom recovery in order to install a custom ROM.
Editing...ignore what I had posted in this space before.
The second link (starts with "Failing that...") says it works with 1.5.
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Helgaiden said:
You have to be rooted to have a custom recovery. This i know...but can you have a custom recovery without being rooted? I dont care about getting this phone rooted, i just want a custom recovery on it.
Click to expand...
Click to collapse
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
roirraW "edor" ehT said:
You HAVE to be rooted to change: recovery, kernel, hboot, ROM, and radio. The only exceptions are official updates, whether they be OTA or running a RUU update from Windows with the phone connected.
Root access effectively means being able to change things you're not normally allowed to change.
If you want a custom recovery on your phone, you're going to have to root it. To be technically fully rooted, you would probably have to change your hboot (referred to as S=OFF), too, but it doesn't sound like you need that part. This may not be the answer that you want, but it is what it is.
Click to expand...
Click to collapse
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Helgaiden said:
Okay, i will try one of those other root methods then. Do any of them install a custom recovery as part of the process like the universal one click root does?
Click to expand...
Click to collapse
I'm sure they all probably do, but I'm sure they say definitively in their threads, too. Everyone who roots wants to install a custom recovery so that they can flash rooted ROMs. Most everyone, anyway. Only those who just want the stock ROM but rooted wouldn't care about the recovery, but those are a minority.
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Helgaiden said:
Alright cool. Im gonna do the last method from Scary Allen's post. Just a question though..
i hook up the phone to the PC then click install_root.bat. That should do what i want, however in what mode should the phone be in when i have it plugged in? Powered on like normal, in the stock hboot/recovery mode...??
Click to expand...
Click to collapse
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
MAKE SURE YOUR SDCARD IS NOT MOUNTED TO YOUR COMPUTER OR THIS WON'T WORK!!!!
Click to expand...
Click to collapse
roirraW "edor" ehT said:
You should keep questions about various methods of doing things in the original thread. If it doesn't say in the thread about what mode it should be in, then you'll have to ask GrdLock. If it doesn't specify then maybe it doesn't matter what mode it's in. The only thing it specifies is:
Click to expand...
Click to collapse
yeah i got that much out of it. Okay, thanks for your help.
The jcase "One Click" .apk does not work on 1.5, as you discovered.
Note that the root exploit method that One Click employs does work on 1.5 - but unfortunately the One Click app itself only runs on 2.1.
The Universal Eris Root for Dummies! method will work on both 1.5 and 2.1; it uses the same (wag3slav3) rooting exploit, but does not require the 2.1 OS to be running in order to work correctly. All it does to your phone is to install the Amon_RA custom recovery - exactly what you are looking for.
This method is the same one referenced by scary alien in his post mentioned above - the second URL in his post.
I've said this before, but I'll say it again: when you say "rooted", it means different things to different people. The most general definition is that you have "installed something on your phone which gives you privileges to alter some or all of the phone software which the device manufacturer did not intend".
So - you can have an engineering bootloader on a phone, but a completely stock OS... and that would be a "rooted" phone. Same deal for a set of root tools installed in the OS, but a S-ON bootloader and a stock recovery partition. Or a stock bootloader, a stock OS, but a custom recovery - again, that is also a "rooted" phone. In all three cases, you now have the means to alter whatever you want on the phone. That's all that "rooted" really means; it doesn't necessarily mean that the OS has been kanged up.
bftb0
ahh confirmation it doesnt work on 1.5, nice haha. Well thanks. Ill look into the Dummies root method but right now im leaning toward's GRDLOCK's method. At least i know i have good valid options though, thanks!
Hey Everyone,
So, I'm pretty sure I'm going to unlock the bootloader on my Prime, but I had a quick question before I do, and I'm not seeing any sort of threads which help me out that much (Or at least the ones I looked at).
To make the story short, I'm looking to be able to root my tablet and install a custom ROM on there, however, it is to my understanding that there is no way to root the .21 firmware at this time. However, I was wondering if by unlocking the bootloader I would be able to manually push CWM Touch and thusly be able to boot into recovery, installing a rom that is pre-rooted, or even just rolling back to a previous update. I'm fairly familiar with ADB and terminal commands, so I am not shy to get into the nitty gritty if need be.
I apologize in advance if this has already been answered or asked, but, I'm in a time crunch and was looking for some advice !
Thanks for the information,
Horvaticus
Horvaticus said:
Hey Everyone,
So, I'm pretty sure I'm going to unlock the bootloader on my Prime, but I had a quick question before I do, and I'm not seeing any sort of threads which help me out that much (Or at least the ones I looked at).
To make the story short, I'm looking to be able to root my tablet and install a custom ROM on there, however, it is to my understanding that there is no way to root the .21 firmware at this time. However, I was wondering if by unlocking the bootloader I would be able to manually push CWM Touch and thusly be able to boot into recovery, installing a rom that is pre-rooted, or even just rolling back to a previous update. I'm fairly familiar with ADB and terminal commands, so I am not shy to get into the nitty gritty if need be.
I apologize in advance if this has already been answered or asked, but, I'm in a time crunch and was looking for some advice !
Thanks for the information,
Horvaticus
Click to expand...
Click to collapse
um...sorry....it might come across as harsh but you didnt look did you? If your familiar with ADB then you should know that rooting has nothing to do with custom roms. In order to put a custom rom you have to have an unlocked bootloader.
Review the Android development Section for info on roms/bootloaders/rooting
An unlocked bootloader was released and we had a rom available within 2 hours.
If you go to ANY thread with [ROM] they will tell you what you need to do. Easy.
And .21 is cooked into many Roms so far...i'm using virtous Prime and prefer that one so far...(it's really about preference)
So...moral of the story..please read before posting...do a quick search...it's been answered before.
monkeyboywa said:
um...sorry....it might come across as harsh but you didnt look did you? If your familiar with ADB then you should know that rooting has nothing to do with custom roms. In order to put a custom rom you have to have an unlocked bootloader.
Review the Android development Section for info on roms/bootloaders/rooting
An unlocked bootloader was released and we had a rom available within 2 hours.
If you go to ANY thread with [ROM] they will tell you what you need to do. Easy.
And .21 is cooked into many Roms so far...i'm using virtous Prime and prefer that one so far...(it's really about preference)
So...moral of the story..please read before posting...do a quick search...it's been answered before.
Click to expand...
Click to collapse
Well, I know that rooting has nothing to do with Rom installment. Admittedly I was posting from a golf course and didn't take the time to sift through the threads. So, thanks for answering my question, kinda. When I said Root & Install a custom Rom I did not mean that in sequential order. Simply that I would like a Rom that has root baked into it, or be root-able.
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
reNeglect said:
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
Click to expand...
Click to collapse
you need root access to flash cwm from rom manager, afaik.
Sent from my TF201
reNeglect said:
Unlock your device via Asus's unlock tool app.
Download and install Rom Manager from Market.
Install CWM via Rom Manager.
Download the rom you want to flash and transfer it to your tablet.
Reboot into CWM and make your first nandroid backup.
Wipe Cache/Factory reset.
Wipe Dalvik Cache
Flash the rom and reboot.
Click to expand...
Click to collapse
Yeah, you do. But I unlocked it via the unlock tool APK and then from there just installed CWM via fastboot and pushed the rom and crap to it. Thanks! Installing now!
Before I begin, Mods, PLEASE pin this. I (when I was a noob) had absolute difficulty installing ROMs. This is very noob-friendly, fixes Status 7 errors, and is easy to follow.
Alright friends and future flashers. I used to have difficulty installing ROMs. Now that I know how (after going through numerous tutorials), I'd like to make it easy for ALL of you. Enjoy your Custom ROM!
Before beginning, you need Android's SDK,Flashtool and The latest Official firmware.
If ever your phone needs to install drivers, let it install, don't unplug the phone or whatever.
And, battery at least 30%. Mine does it at even 20% without issues, but just to be safe.
Step 1: Revert to Stock
You don't need to downgrade. After flashing the latest stock kernel, I have flashed every single GB and ICS ROM in existence without issues, so you don't need to flash a specific one. But, latest one tends to be more stable. Here's what you do:
Get the latest Global ftf for your phone. Then, flash it using Flashtool. I won't go into specifics, but PM me if needed
By Now, you should have a stock EVERYTHING. Boot up the phone, run through the whole set up process. Once you are done, you need to get your IMEI number. Do this by following the steps here.
In the end, you should have the bootloader unlocked. If you come up with something like bootloader already unlocked, then you are good to go. Now onto......
Step 2: Preparing your Flash.
Download the ROM of your choice. I'd recommend FXP's Unofficial CyanogenMod9 as it has the best stability and no ICS Multitouch issues. If it is GB, any ROM will do. Most of them are stable.
Now, in the case of CyanogenMod, they often come with their own custom Kernel. It is in the zip file, known as boot.img, and you simply extract it to your platform-tools folder in the android-sdk folder you downloaded to unlock the bootloader. This is also true for some MIUI ROMs I've come across. Read their forum posts for more info on which kernel to use.
Copy the ZIP file to your sdcard. It does not have to be the root of SDcard, anywhere will do.
By the end, your Custom ROM's ZIP file will be in your SDCard, and the kernel file (a.k.a. boot.img or whatever_the _kernel_name_is.img) will be here:
32bit Windows: C:/Program Files/Android/android-sdk/platform-tools
64bit Windows: C:/Program Files(x86)/Android/android-sdk/platform-tools
Now we can
Step 3: Flash your Custom ROM
In the folder above (depending on OS version) press Shift+RightClick. Options will show up. Select "Open Command Prompt Here". A Command Prompt will open (duh).
Turn off your phone. Wait 10 seconds. While plugging in your phone, press the Menu button (the Right button). The LED Indicator should turn blue. This shows your in fastboot mode. If it starts to boot, rip out the battery and try again. DON'T STOP PRESSING UNTIL IT TURNS BLUE.
Now, type EXACTLY AS FOLLOWS, ONE AT A TIME. Just type in the lines with the "-" before it, but don't put in the "-" when typing it. The line underneath in brackets is an explanation, so you understand what is happening.
-fastboot devices
(This is actually a quick test I do to see if my phone is connected in flash mode or not. If nothing happens, it is not in flash mode or the drivers are installing)
-fastboot flash boot boot.img
(This is telling fastboot to FLASH the BOOT partition of your phone with the file specified. If you are using a different kernel, simply replace boot.img with the name of the kernel, ending with .img and wait for it to finish. Won't take long)
-fastboot reboot
(This causes the phone to reboot)
Now, while it is starting up, keep repeatedly pressing the Volume Down button until you are in ClockWorkMod Recovery (Assuming you are using it. CWM is the most popular and most kernels use it) Then, If you choose to, make a backup. I personally don't, as it is not too big an issue and I never revert to an old ROM anyway.
After that, choose Factory Reset. This will remove ALL data in your phone except your Stock ROM. Then, Clear Cache. You might've noticed it already did that when you Factory Reset, but this is for safety. Finally, in advanced, Wipe Dalvik-Cache and Wipe Battery Stats. I do this all the time for safety.
Now, the fun bit. GO to Install ZIP from SDCard. Select Choose ZIP, find your ROMs ZIP file, and install. It might take awhile, but not too long. Just be patient. When it finishes, flash anything else the ROMs forum post says to flash (Gapps, Patch, etc) and select Reboot Phone.
Step 4: Done!
Your phone will start up. First time is always slow, but this WILL WORK. Congratulations. You now have a Custom ROM
If you get a Status 7 error while flashing a ROM, reboot recovery and wipe everything again. If that doesn't work, flash official firmware and try again.
Credits to:
-Google: Providing Android SDK and Gapps
-Androxyde: Flashtool
-Madfysh: List of Official ICS ROMs
FXP: Creating CyanagonMod9
-And YOU!
P.S.: If you're confused, or feel this could use something extra PM me.
And uh, if it needs to be moved, please do so. Thanks!
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
PLEASE Don't spoil the mood man!!
This is a development section where even Noob Devs know how to flash a Custom Rom!! PLeaseee Pleaseeee ... Move it
Alright man. How would I move it? Cause, I only RECENTLY started being active on the forums.
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Reck1993 said:
Don't say that thread is unnecessary; they put everything in one thread cause it's easy to find. the first step we should do is rooting if we are noops. Then we will be curious about unlock or custom rom later.
Sent from Xperia Neo using AOKP B40
Click to expand...
Click to collapse
Okay. I will add an easy rooting instructions to it.
kormatoes said:
Still dev thread so if you don't know how you should not be trying
It goes like this no dl link no thread
but still is a good post
some unnecessary parts
some dodgy parts
But good for noob never-ending Questions
Maybe Q&A
Click to expand...
Click to collapse
Thanks kormatoes. Could you gimme some of the unnecessary/dodgy parts?
Jass5991 said:
I do know there is THIS but I felt some of his steps were unnecessary. Example, rooting. Any custom ROM will be rooted, so there will be no need to worry about that. And he also provided overclocking tips and an unofficial bootloader unlock which are hazardous and potentially permadamaging to the phone.
Click to expand...
Click to collapse
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Madfysh said:
1) actually that(which you linked) tutorial is good, it just need some updating. but your tutorial is different than that.
2) root is certainly not unnecessary! not all people will go for custom roms, specially as most of them are for unlocked BL.
3) unofficial unlock is not hazardous, it is tricky, but it paid of if we look on the advantage against official unlock
Nice from you that you wrote all this, it's based only for custom roms's, thread which is already sticked is for basic things, which any noob should know.
But still, this looks kinda cluttered, and from noob(which you intend this to) point of view, to long/complicate to read
Click to expand...
Click to collapse
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
lalit387 said:
Thank you all big guns
but there should be a start-up kit for newbie
There can be a Starter Section with due permission
Click to expand...
Click to collapse
As it is, I am attempting to code a batch file to automatically run the entire flashing process, including kernel and ROM. Having a small issue where it does not wipe dalvik and cache. It also doesn't flash the custom ROM
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
kasem71 said:
hallo guy
(first, my english is bad because i am from germany)
i have installed safestrap and the rom slot 1. i installed/flashed at the rom slot 1 thor gapps rom. after starting the system it came in a bootloop. so safestraped asked me to stop and format it. i thought it means only the rom slot 1. after that on safestrap is the stock rom empty and the other slots too. when i try to make a new rom slot it say there is no space. at the stock rom is only 1230mb space at the system partition. but there is no os. when i try to conect it on my laptop. the laptop dont recognize the kindle. so what can i do ?
Click to expand...
Click to collapse
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Arashkage said:
If I remember correctly you have to do these steps after installing the safe trap.
1. create back up from stock rom
2. Create romslot 1
3. restore the back up on romslot 1
4. install the thor gapps rom on rom slot 1.
thor gapps need the stock rom first. that why you create back up and restore it somewhere else. thor gapps is NOT a AOSP room, it removes and modifies the stock rom.
I don't think you can format your stock rom but if you did, you have to wait for a AOSP rom.
Click to expand...
Click to collapse
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
if
kasem71 said:
the problem is that i cant put anything on my kindle. the laptop dont recognize the tablet. so if a rom come out i cant put it on my kindle. the stock rom is there but its empty !
Click to expand...
Click to collapse
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
jimyv said:
If you could if you can get somebody to send you a backup of some type you can ADB push it to your Sd card in backup directory and restore it . What is your base firmware originally? If you can score a flashable copy of your base that would work also. Four instance the base Hasscode has over in the safestrap thread. (Old firmware) But to get ADB you need to uninstall the Microsoft USB drivers for your device and install the ADB drivers from the utility .94
Click to expand...
Click to collapse
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
sorry
kasem71 said:
thanks for you help. the firmware was the newest. 13.3.2.4. and can you give a step by step tutorial for the ADB ? i wont make it wrong, again
Click to expand...
Click to collapse
You dont already have the toolkit from development?it has adb drivers try that first .does your device show at all? Maybe with like an explanation point on it and the yellow triangle? If it does open that device in your device manager in and uninstall the drivers. Then run the driver install part of the utility toolkit .94. I'm sorry but no I cannot give you step-by-step or I will not considering it is in these forums at least a dozon times but I'll give you a link to a thread that explains it over and over again but you must be able to comprehend what you are reading and follow directions explicitly it does work it has worked for people but sometimes it takes several attempts . http://forum.xda-developers.com/showthread.php?t=2588608 remember but not just the first post has good information this is discussed all the way through these threads . And often pertain to different subjects . And if you don't think that you find what you need in this thread there are several several other threads in the general section and the troubleshooting section titled brick! Or please help! Or yada yada yada etc. and most will have to do with trying to get ADB back on a device.. For whatever reason. What ever you do do not go to factory recovery attempt a factory reset it will totally screw you. As long as you still have safestrap booting you have hope now you need to do what you did not do to begin with,and educate yourself thoroughly before moving forward with anything . All it will take is one more mistake on your part of the inability to completely read everything and understand everything and you will be calling Amazon for a replacement.. good luck why can't you restore a backup?
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
kasem71 said:
hallo
my english is bad, so its diffcult to understand everything. because this i ask for a step by step tutorial. this was my fault.
and is there a difference between the 13.3.2.4.X.X.X versions ? can i take any 13.3.2.4 back up ?
Click to expand...
Click to collapse
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
jimyv said:
Yes. As long as long is it is of a stock system of the same firmware you are on. I am aware of how to do it how to give you a clean backup that would allow you to set it up but I am not on that firmware on any of my three HDX devices And then another idea you may go over to the safestrap thread and inquire about a ABD sideload procedure I did see that option and safestrap recovery but I do not know how it works. Oh and another idea I also know works because I advised it to another person and he did it it worked well for him in a similar situation. Download the original bin file for your firmware to your PC rename the .bin to .zip and download the newest flashable superSU ADB push to SD card then flash to stock slot. Firmware then supersu reboot, reinstall safestrap and redo OTA blocker. It also sounds like you really need to read through the safestrap thread and understand it more thoroughly I do not believe this would've happened if you had more of an understanding on how safestrap is to be used.
Click to expand...
Click to collapse
when i do this, can i install updates from amazon ?
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
No!
kasem71 said:
i cant post anything on the development topic. when i do this, is the device like after a factory reset ?
Click to expand...
Click to collapse
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file BUT safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device AND YES IT will overwrite any system modifications and root access that's why you must flash the super SU after you flash the firmware zip if you want root right away..that is
jimyv said:
Didn't you read in a previous post a couple of post up do not factory reset at least until after you get a working OS and yes you can flash and Amazon bin file that safestrap does not flash kernel or bootloader so it will only flash the system partition and data partition and that is what you need. But you have to rename it from .bin to .zip and somehow get it on your device
Click to expand...
Click to collapse
ok thanks
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
It doesn't matter
lekofraggle said:
If you are still having trouble, go to the developer thread, and rather than posting, try reading and getting the HDX TOOLKIT .94 to work on your computer. That should get adb set up for you. Once that happens, the commands are easy.
$adb push [file location] /sdcard
Click to expand...
Click to collapse
He didn't listen he chose to do in ADB sideload through safestrap and completely screwed it up now. As far as I know he still has not recovered this device