Related
Its been done on the Incredible and Evo, now the Slide. This SHOULD BE IT. Here is their post with exact method. Adjust for the N1 and test on an unrooted phone. ASAP. This should be it!!!!!
QUOTED FORM EUGENE373 @ MT3GS FORUM:
Originally Posted by brokensanity
How-TO Root the Slide
First!! - Go to Settings > Application > Development and turn on USB Debugging. This should save you headaches.
NOW… Power Off the Slide
Download This Package > Slide Root.zip
kingofyo1's Video How-to > http://www.youtube.com/watch?v=sVjoKvy-YZg
Step 1.
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
Step 2.
Open Command Prompt or Terminal and CD to the SDK/Tools Directory.
Step 3.
Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button )
Step 4.
Now run your loop file from the prompt (either type "loop" in windows or "./loop.sh" in a *nix like)
Step 5.
Once your loop is running in your prompt, select Recovery from the bootloader menu.
Step 6.
When recovery loads, you should Have an Offline Device. You can use ctrl+c to stop your script & see.
If this doesn't happen, Power Off and try again..
Step 7.
Un-plug your USB cable from the back of your phone & Plug it back in for it to Detect ADB Correctly!!! This is an important step. At this point you can adb devices to see if you can see your device and that it is in recovery mode.
Step 8.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
Step 9.
adb push ota.zip /sdcard/update.zip (*nixlike users add a ./ in front of all terminal commands please.)
Step 11.
adb push slideroot.zip
Step 12.
This is Very important!! Have this Command ready in your prompt before applying update.zip again!!
adb push update.zip /sdcard
step 13.
Hit run update.zip, as soon as you see a Little Bar appear under the text push Enter to execute the command in your prompt (adb push update.zip /sdcard )
Step 14.
In successful, you should see Clockwork Recovery. If unsuccessful, repeat steps 12 & 13.
Step 15.
Now, go to the Partitions menu and Mount System
step 16.
Go back one level & select install any zip from sdcard. Select slideroot.zip & apply update from zip (This will finish the Root process).
Step 17.
Reboot your phone & wait for it to load completely. To confirm that your slide is connected as a device use the command adb devices. If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root.
Congrats.
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method
Why don't you test it out and let us know the results? ;-)
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Im waitn for someone to try this out... hahaahah
b9nez said:
why do we care about the bootloader since both HTC and Google are ok with us unlocking it?
Click to expand...
Click to collapse
If people don't unlock the bootloader they get to keep their warranty
PhantomRampage said:
If people don't unlock the bootloader they get to keep their warranty
Click to expand...
Click to collapse
Most of the time, they'll replace our equipment. It's been done before, i'm witness to that.
I don't argue this would be a good idea but it's not THAT necessary. :\
Edit: only real upside i can see is getting rid of that annoying unlock icon but since i'm already unlocked there's no point.
This would be pretty good for people like me, who has an unrooted Nexus One
whorehay said:
This would be pretty good for people like me, who has an unrooted Nexus One
Click to expand...
Click to collapse
The key is that we need a DEV with an unlocked phone in hand. I can switch my purple-tinted screen out and get it over to a good one, but that could take a few weeks, anyone else have the tools ready?
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
If it is messing with just the image then im 99% sure yeah you can.
I have a mytouch slide also and this method works. Were having problems getting a recovery to stick on the phone though. I have no idea if this works on n1. Id try but my bootloaders already unlocked.
Santoro said:
I read that whole thread and there was no mention of bootloader at all. If someone can confirm it isn't touched I might be willing to give this a go with my new ATT N1.
If I somehow manage kill it, is there a way to recover a stock image without root?
Click to expand...
Click to collapse
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
FishFan319 said:
I can say that it wont hurt the phone. I tried a process similar to this before I had the details with one of the better known devs from XDA this weekend for a few hours. Even though we couldn't get the timing right, at the end of the day, I still had my original Rom, and it haven't even been hit with a recovery.
Click to expand...
Click to collapse
So I know just enough to be dangerous. I need to understand a little more before I try this on my N1.
This slide_root.zip, are it's contents phone-specific? You said we should modify the process for the N1, are you saying that the contents of the file need modification? Or just the navigation around the recovery?
I am pretty leery until I understand what the slide_root file does and if it is compatible with my phone. Anyone know?
If I do it and it fails, does anyone have a link to how I would reinstall a stock image via USB?
edit: grammar
I developed a screen problem and had to pay to get it repaired because the bootloader was unlocked. Nothing to do with ROM or anything, a section accross the top of the screen went unresponsive to touch. So I know for a fact that they DON'T always honor warranty after unlock. I guess I must've gotten the a*hole operator/technician then for my call...
Jr33 said:
i have exchanged my N1 with an unlocked bootloader without any issues. and many other people have as well. if its a hardware issue they will ALWAYS honor warranty. if your phone is bricked by something you flashed they won't honor that
Click to expand...
Click to collapse
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Santoro said:
That really is a matter of interpretation by the tech you get at HTC. Based on the poster just above this, the warranty is not ALWAYS honored. Right?
Click to expand...
Click to collapse
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
kaiser_tytnii said:
right. I could not get mine repaired for the dusts under screen problem with unlocked bootloader.
I think most of them slipped through since they could swap in US
Click to expand...
Click to collapse
I stupidly got mine etched. Had I thought about the fact that it would preclude me from getting cross-shipped warranty work, I'd have reconsidered.
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
bobtentpeg said:
I WISH I COULD TYPE IN ALL CAPS IN TITLES TOO...
Anyway....
I'm assuming the OP didnt intend for yet another thread to devolve into the warrantly debate.
Click to expand...
Click to collapse
yep, i agree. let's stop the warranty debate here.
i probably will find someone who has a unrooted phone to try it out
I have been reading the http://forum.xda-developers.com/showthread.php?t=1006368&highlight=mac+osx thread (DesignGear's aRoot script, edited to run on Mac OS X)
My phone is connecting fine in USB debugging mode. The script runs but it doesn't seem to be working quite right. There are many files failing to copy.
Here is what I get when I run the script...
Getting temporary root access...
861 KB/s (585731 bytes in 0.664s)
Mounting /system as read/write ...
Cleaning up onclickroot mess ...
Rooting your device ...
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/su' to '/system/bin/su': Read-only file system
Installing Superuser app ...
878 KB/s (196521 bytes in 0.218s)
Installing sqlite3 ...
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/sqlite3' to '/system/bin/sqlite3': Read-only file system
Enabling sideloading ...
Enabling tethering ...
Enabling init.d support ...
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/install-recovery.sh' to '/system/etc/install-recovery.sh': Read-only file system
failed to copy '/Volumes/Documents/Android/aRootMac_fix/bin/00remount' to '/system/etc/init.d/00remount': No such file or directory
Rebooting ...
Press any key to continue...
Then it reboots.
Superuser is installed, but I don't know if the process is successful or not. I'm also not sure what to do next.
This is my first post here and my first attempt at rooting, though its my third android device.
Thanks for your help in advance.
Nick
Depending on the software version of your Atrix.... aRoot doesn't work anymore.
(The part that is likely to be failing is psneuter, which was fixed by motorola a few software revisions ago)
You can check by opening SuperUser.apk and click on 'check su version' and if it fails, you don't really have root.
I too, am an OS X user.
As far as I know there is no way that actually works to flash your phone from OS X.
And I don't think there is any way to root anymore without flashing. (somebody can correct me if I am wrong)
I installed windows XP on a boot camp partition and installed RSDLite and moto-fastboot and unlocked/installed alternate ROMS.
http://forum.xda-developers.com/showthread.php?t=1136261 is probably where you should start.
dragula53 said:
As far as I know there is no way that actually works to flash your phone from OS X.
And I don't think there is any way to root anymore without flashing. (somebody can correct me if I am wrong)
Click to expand...
Click to collapse
Actually, for flashing this is not true. sbf_flash works fine.
OP, you should do a search for that. I'm on an MB Pro OS X 10.7.1. In fact, it worked where my Vista 64 bit machine + RSD lite wouldn't. I've used it several times to unlock the boot loader (IHOP_Bell.sbf). It worked flawlessly. After that, flash clockwork mod with moto-fastboot-osx64 or 32, and then you can just look for a ROM to install from cwm that is already rooted... which most of them are.
Based on the command line output, remounting the system partition for read/write failed, probably due to the "getting temporary root" step failing also. This means you don't have root because su wouldn't be copied over properly. aRoot is for 2.2.1... What version are you on?
Thank you both for you reply's.
I tried to check SU version and nothing happens, so I guess it's not rooted.
Also I checked my android version and I'm on 2.2.2 so I guess aroot's not for me.
I will try the RSD lite option next I guess..
Thanks again
Nicholox said:
Thank you both for you reply's.
I tried to check SU version and nothing happens, so I guess it's not rooted.
Also I checked my android version and I'm on 2.2.2 so I guess aroot's not for me.
I will try the RSD lite option next I guess..
Thanks again
Click to expand...
Click to collapse
Really, the RSD lite option? Why would you go to all the trouble of bootcamp and Windows when you could do it all on your current OS? Even some Windows users will tell you how frustrating it is to get RSD lite working on some machines. Works great on my netbook with Win7 Starter, but my main Win Vista 64 bit wouldn't do it no matter what.
For OS X, you just need:
sbf_flash
moto-fastboot-osx
Use the International Pudding thread as a guide to unlocking your bootloader. Once you've done that, the subject of root is almost moot because most ROMs are already rooted, you only need to install superuser.
Yeah I guess you're right I would prefer to do it on in OSX. I do already have a windows partition setup though, but I would rather not use windows if oI don't have too. It's just that in your earlier post the process sounded more complicated compared to the RSDLite option, which I have also already read a little bit about.
I have downloaded the files, but I'm not quite sure where to go from there. From what I can gather I need to unlock the bootloader first. But what do I do with the sbf_flash?
Thanks again
Nicholox said:
Yeah I guess you're right I would prefer to do it on in OSX. I do already have a windows partition setup though, but I would rather not use windows if oI don't have too. It's just that in your earlier post the process sounded more complicated compared to the RSDLite option, which I have also already read a little bit about.
I have downloaded the files, but I'm not quite sure where to go from there. From what I can gather I need to unlock the bootloader first. But what do I do with the sbf_flash?
Thanks again
Click to expand...
Click to collapse
Okay, well first of all, you need to flash the unlockable bootloader:
1. Turn off your phone, then hold the down volume button and tap the power button. The phone will start up with a cycling menu that initially says, "fastboot".
2. Press volume down several times until it says, "rsd". This is the mode you want to be in.
3. Press volume up to select this mode.
4. Open up Terminal, cd to where your files are and type:
Code:
./sbf_flash IHOP_Bell.sbf
5. Reboot your phone and hold down the volume button again. This time you want to be in "fastboot", so when it comes up, press volume up.
6. From Terminal, type:
Code:
./moto-fastboot-osx64 oem unlock
Use the 64 bit or 32 bit version of the commands depending on your system. If you're on Lion or have a pretty new computer, it'll be the 64 bit one.
It will tell you to type in that command again, but this time along with the id they've provided. Take a look at the screenshots in the Pudding thread, they basically show this step, but in a Windows command prompt. It's the same thing.
7. Reboot your phone:
Code:
./moto-fastboot-osx64 reboot
Now you can flash clockwork mod onto the recovery partition with moto-fastboot-osx also. The ORFR 2.3.4 thread has some good examples and instructions on general flashing. The gobstopper threads also have some recovery files and instructions you could use to start off. Once you've got recovery installed, you're pretty much in the clear. You can softbrick your phone, but with recovery it's easy to get back to a working state.
Good luck!
Hey thanks Maledyris, this is great. I had some trouble finding the IHOP_Bell.sbf but I have it now.
I also found the ORFR 2.34 system and webtop images, what is the difference between these and the HKTW files, which should I use?
I'm hoping that putting Gingerbread on this phone will improve my signal strength (I read this somewhere online). If it doesn't I would like the option of returning it and getting a different phone with proper reception. How much of this can be undone? should I need to?
when I unrared IHOP_Bell.rar I got intl-fix-try1.sbf
Is that right?
Sorry this is my first time and I'm totally noob and a bit nervous.
Hey one more question, I saw another post of yours from march and it said you'd gone back to 2.2.2....what are you running now??
Cheers,
Nick
Nicholox said:
when I unrared IHOP_Bell.rar I got intl-fix-try1.sbf
Is that right?
Sorry this is my first time and I'm totally noob and a bit nervous.
Click to expand...
Click to collapse
Well, I did it weeks ago, and back then it was actually called IHOP_Bell.sbf. It's possible the poster re-uploaded with a fixed version... Did you get it from International House of Pudding thread? If you did, that's the right one.
Nicholox said:
Hey one more question, I saw another post of yours from march and it said you'd gone back to 2.2.2....what are you running now??
Cheers,
Nick
Click to expand...
Click to collapse
Yeah, I'm currently on stock 2.2.2. I'll have time this week, so I'll probably play around with some of the newer ROMs people have been putting out. Before this, I had to go back because of stability and battery problems
Nicholox said:
Hey thanks Maledyris, this is great. I had some trouble finding the IHOP_Bell.sbf but I have it now.
I also found the ORFR 2.34 system and webtop images, what is the difference between these and the HKTW files, which should I use?
I'm hoping that putting Gingerbread on this phone will improve my signal strength (I read this somewhere online). If it doesn't I would like the option of returning it and getting a different phone with proper reception. How much of this can be undone? should I need to?
Click to expand...
Click to collapse
Ah, uhh... I'm not sure about the whole undoing part for you. I'm on Bell, and Bell has packages under the gobstopper threads to go between stock 2.2.2 and the alpha 2.3.4. I don't know if anyone has made the same type of thing for Telstra? Someone who's on Telstra could look at the images that were created for the Bell 2.2.2 stock cwm recovery and do the same for Telstra. I think it would depend on your carrier whether they care if you've unlocked your boot loader and changed the firmware? I've never tried to return my phone, but I bet they don't check. You never know though.
If reception and the radio is your main concern, I would probably see if I could just flash the radio instead of trying to flash full ROMs. It would be less of a noticeable change if you did decide to return it. I don't have suggestions on that though, you'd have to do a search. I don't quite remember anymore, but I think I flashed either the Orange or Telstra radio ages ago before we had an unlocked bootloader. It was fairly quick and painless. I had done it with RSD lite and win7 before I knew sbf_flash existed.
maledyris said:
Really, the RSD lite option? Why would you go to all the trouble of bootcamp and Windows when you could do it all on your current OS? Even some Windows users will tell you how frustrating it is to get RSD lite working on some machines. Works great on my netbook with Win7 Starter, but my main Win Vista 64 bit wouldn't do it no matter what.
For OS X, you just need:
sbf_flash
moto-fastboot-osx
Use the International Pudding thread as a guide to unlocking your bootloader. Once you've done that, the subject of root is almost moot because most ROMs are already rooted, you only need to install superuser.
Click to expand...
Click to collapse
Awesome. I wasn't aware that there were OS X versions now. I flashed very early on though, and never checked again.
And if you are looking for newer ROMs, I highly recommend Ninja ROM, which is my favorite of the bunch that still retain all of the Blur applications.
... Or CM7 pre-beta 2, which breaks the camera in most apps that use it. Pre-beta 1 ruined my battery life, but beta 2 is just fine. If you go this route and still want to use the camera, Angel Camera on the market works.
Thanks again Maledyris,
I did get it from the international house of Pudding thread so it must be the right one.
I found this thread http://forum.xda-developers.com/showthread.php?p=16853634#post16853634
They are talking about the motorola defy.... do you think that 2.2.2 will work with the Atrix too?
Dragula, can you give me some links for those ROM's you're talking about? I would like to use the camera still I think!!
cheers!!
ok heres the latest, my Atrix has gone in for a repair. It had some serious reception issues and after a week of arguing with telstra they're going to have a go oat repairing. it. Basically it show lower signal strength than many other phone. If you're here Aus you'll know Atrix is supposed to be "blue tick" well this one certainly wasn't.
Anyway my rooting plans are on hold till I get the phone back...
any chance of those links dragula?
Are you still around Maledyris?
I got my phone back and it's no different, so I'm ready to get started. I've read through your instructions again, and tried to find an answer elsewhere in the forum, but I'm still confused about how to flash CWM recovery the bootloader is unlocked. There seems to be so many files and I'm not sure which are ok for my telstra atrix.
I saw I can download CWM from the market, is that what I need to do next? but you said flash CWM so I'm guessing not the market...
I've downloaded recovery-en-goapk-0630-1029.zip but I'm not sure exactly what to do with it??
Thanks again,
nick
Hi Nicholox;
I am in he same boat as you. I am about to get my first Android Phone (looking at the Atrix) and have been doing some serious reading about bootloaders/rooting and ROMS.
How did you unlock your bootloader?
Now to answer your question on CWM. From what I have read you can download and install ROM Manager from the App Market and then use the ROM Manager to install CWM.
I am pretty sure thats right. Someone please correct me if I am wrong.
Just check out these intructions from Maledyris... I'm not sure if my phone will boot up to access the market after flashing the sbf and unlocking it. anyone know the answer to this?
maledyris said:
Okay, well first of all, you need to flash the unlockable bootloader:
1. Turn off your phone, then hold the down volume button and tap the power button. The phone will start up with a cycling menu that initially says, "fastboot".
2. Press volume down several times until it says, "rsd". This is the mode you want to be in.
3. Press volume up to select this mode.
4. Open up Terminal, cd to where your files are and type:
Code:
./sbf_flash IHOP_Bell.sbf
5. Reboot your phone and hold down the volume button again. This time you want to be in "fastboot", so when it comes up, press volume up.
6. From Terminal, type:
Code:
./moto-fastboot-osx64 oem unlock
Use the 64 bit or 32 bit version of the commands depending on your system. If you're on Lion or have a pretty new computer, it'll be the 64 bit one.
It will tell you to type in that command again, but this time along with the id they've provided. Take a look at the screenshots in the Pudding thread, they basically show this step, but in a Windows command prompt. It's the same thing.
7. Reboot your phone:
Code:
./moto-fastboot-osx64 reboot
Now you can flash clockwork mod onto the recovery partition with moto-fastboot-osx also. The ORFR 2.3.4 thread has some good examples and instructions on general flashing. The gobstopper threads also have some recovery files and instructions you could use to start off. Once you've got recovery installed, you're pretty much in the clear. You can softbrick your phone, but with recovery it's easy to get back to a working state.
Good luck!
Click to expand...
Click to collapse
ok this doesn't seem to be going so well. I finally psyched myself up to unlock my atrix and i'm stumped at the first step.
Nicks-MBP:Atrix Nicholox$ ./sbf_flash int-fix-try1.sbf
-bash: ./sbf_flash: Permission denied
Why do I get a permission denied when I try to flash bell IHOP?
thanks,
Nick
i have been seeing a lot of threads about rooting this phone, but, they all have windows scripts, even the thread that is said to have a runme.sh does not have it in any of the links that i unzipped - only a runme.bat, but yet, people keep mentioning a runme.sh in it... also, i really don't see any one lying out the steps for doing this with linux.
i'm a noob, and dont really know much about this stuff, but i've done this ONCE before with a galxy exhibit, but it was very easy, i just copied a file to the phone (stock rom?), rebooted into recovery, told it to recover from that file, and i was done.
i have no idea how to do it with my new phone, and so i'm wondering:
1: where can i find the files i need to do this with linux - i just want root, nothing special
2: where can i find the steps necessary to do it - in the easiest manner possible?
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
any help is appreciated.
sentientsystem said:
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
Click to expand...
Click to collapse
Your phone is running ICS 4.0, that is the version which it shipped with. Pretty much everyone on here has upgraded to JB either with software update on the phone or they have manually updated with the offline KDZ flash method.
I dont have any experience in linux so I cant help. I hope you can get your phone rooted!
Sent from my LG-P768 using xda app-developers app
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
sentientsystem said:
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
Click to expand...
Click to collapse
You would need wine and then set it up...
Sent From My Xperia Themed P769
well, i tried that "LGpwn" and it didn't work, as well as a fake lg-recovery app. i figured out that i've got a "10g" phone (P769 V10G ICS). i'm not sure what the next step is. some one mentioned downgrading to JB... is there some where you can point me to for that???
i've GOT to get this t-mobile junk off my damned phone... i've even TRIED to install cyenogenmod, but i can't figure out how to get my phone to go into recovery mode (NOT factory rest) - i've tried volup+power+home and volup+power, and neither seem to be working.
Setup a sandbox, windows xp. LG uses windows, no other way to root as of right now for the t-mobile version.
Sent from my LGMS769 using xda app-developers app
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrade to a samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
sentientsystem said:
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrad to an samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
Click to expand...
Click to collapse
Option #1
If you are rooted on stock T-Mobile 10e or 10g ROM and have the CWM installed from this thread:http://forum.xda-developers.com/showthread.php?t=2095825 follow my instructions.
Place one of these CWM ROM images on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2136204
Place this JB radio firmware from T-Mobile 20d ROM on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2256350
Power off the device.
After power on the back/menu capacitive buttons will flash repetedly. Press Volume down while the lights are flashing and the phone should go into recovery.
Flash the ROM first.
Flash the radio second.
Reboot.
***Notes***
1.) 20d is the latest T-Mobile, 21b is the latest Wind Mobile. Both work.
2.) 21b is lighter/faster but has no wifi-calling.
3.) 21b will require you to manually enter your APN settings for cellular data and MMS. Be sure to write down your APN settings before flashing this ROM.
4.) Some users say battery life sucks on JB. I notice that 21b is better on battery life than 20d.
Option #2.
In Linux install a Windows VM and follow the standard instructions here:
http://forum.xda-developers.com/showthread.php?t=2173465
Use KVM with a GUI or even easier use VirtualBox.
I'm a die hard linux geek too. I even run linux at work while all of our msp software was written for windows. You are better off just running an old copy of xp inside virtualbox trust me its just easier that way. You can use adb if you like (its the same thing the windows users use in their batch files and just rewrite the bash script, but you will save yourself lots of headaches just using virtualbox. -- my .02
Sent from my LG-P769 using xda premium
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
# what's the difference between unlocked boot loaders and being rooted?
# do you have to unlock the bootloader to get root access?
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
My bad. I should have read through your original question all the way before posting. I see that you are not rooted.
If you are on 10e ROM you can root in Linux:
http://forum.xda-developers.com/showthread.php?t=1990705
It will require rewriting the batch script as a Linux shell script. It is possible but nobody has done it yet.
If you are on 10g you will need Windows. I have also answered your questions below.
sentientsystem said:
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
It allows you to boot an un-signed kernel. You can boot custom ROMs basically.
# what's the difference between unlocked boot loaders and being rooted?
Root allows you to `su -` to the root user and own the whole system.
# do you have to unlock the bootloader to get root access?
No.
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
Click to expand...
Click to collapse
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
sentientsystem said:
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
Click to expand...
Click to collapse
Welcome!
I know that a long time ago when I ran VirtualBox in Ubuntu there was something I had to do to allow USB access to the VM.
Here are the current instructions directly from Ubuntu:
https://help.ubuntu.com/community/VirtualBox/USB
Good luck.
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
sentientsystem said:
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
Click to expand...
Click to collapse
Yes you can flash a pre-rooted image. They are available. Use the search?
I posted instructions on the first page showing how to boot recovery.
that's great news - that's all i really needed - i didn't see them before, at least, not conspicuously, but i'll search around again.
and, i must have some how missed your instructions, i'll look again.
thanks!
kevev said:
I posted instructions on the first page showing how to boot recovery.
Click to expand...
Click to collapse
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @everyone for your help.
sentientsystem said:
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
Click to expand...
Click to collapse
I've decided to help you out This page will give you some more info on the P769 and several kdz (roms) for the P769
The fastest way to root is to flash the V21B kdz (this is the Jelly Bean version for Canada) using this guide, http://forum.xda-developers.com/showthread.php?p=36351786
The reason why you want this rom is because it has a vulnerability that is easy to exploit with Jcase apk
Once your followed everything (and rooted), install Super Su and Busybox
Next install artas182x second init CWM (in case you can't find it on his page, the link is here )
Note: you will see blinking led lights when you see the LG logo (booting up) appear after a couple of seconds. To enter the CWM press the vol (-) when the lights start flashing.
After you installed Artas182x CWM you can recover from someones clockworkmod backup.
following info from Cmahendra's thread
Note: only restore CWM backups from P769 versions or MS769!!!!
Or check out the V10B (MetroPCS "JellyBean") CWM backup
Now the only 2 reasons to unlock the bootloader are:
1. Install a safer and better CWM
The reason why is because Artas182x CWM is a second init (bootstrap), so if you mess around with a busybox apk and something goes wrong or you remove a file that is required (for CWM), it will stop operating. You will have to reflash the kdz or fix what you changed to get it working again.) I've had this problem several times while messing around with different busybox apps and etc.
2. Custom roms
(which you stated you are not looking for) not worth talking about right now.
Answer to questions
The only pre rooted roms are clockworkmod backups, lol
The default recovery is useless to us (unless you feel like solving the problem)
Flashing back and forth (ice to jelly) comes with risk, the program used on Windows to flash is buggy at times. The best way (in my opinion) is to flash only when really required and mostly restore from clockwormod backups. The device is actually hard to hard brick, but it will require at lot more knowledge to get your device running again.
---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------
sentientsystem said:
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @all for your help.
Click to expand...
Click to collapse
So what version are you on right now
Ice? Jelly?
i'm still on ICS for the moment. still trying to understand what i need to do next. re-reading your post for the 2nd time, and all the threads it references. making sure i don't screw any thing up. thinking about upgrading to JB, and trying this CWM. and looking into this "cyanogenmod" some more, to understand why i never see any one on this site mention it, and what all these "other roms" are about. lmao, like i said, i'm way new to this . it's a lot to take in, even for a web developer .
thanks \m/ (>_<) \m/
[update 2] I just summarized a way to backup and restore (all based on other great DEV's work, just put in one place) your TS before your play with your TS here: http://forum.xda-developers.com/showthread.php?p=52820278#post52820278
Go check it if you plan to root your TS!
[update] With the help of cheahcl, I got the latest F/W for 4th List 1/8/2100. With the MTK SP_Flash_Tool, I was able to upload a corrected F/W for my TS and everything goes back to normal!
Thanks for cheahcl for his dump and Lokifish Marz for his All in one tools! You guys really saved my day! (and my TS).
A Quick summary: Do NOT use any method on XDA yet to root or change TWRP recovery! It seems the TS of 4th list is different in some way than the ones before which render most of stuffs here invalid. However, fear not to play around since now we have a way to go back to stock!
In my experience, I found that it's really difficult to truly brick a MTK based system. The system will just reject flashing at slightest sign that a F/W is not compatible. The only cache is you need to have the "correct" F/W specifically for your TS!
In my observation, OMate made changes between each delivery. For Example, the 4th list of 1/8/2100 is different in (At least F/W configuration) of the 3rd or earlier 1/8/2100.
------------------------below is my original story of what I tried and failed--------------------------
Just got mine (1/8/2100) 5 hrs ago! I am on the 4th list. The delivery in FAST!
The watch starts normally. I played with it for a while, than decided to root it, install TWRP and apply the security hack made by +Lokifish Marz
Now I have a brick! Just after 30 min I receive the watch!
<<Can anyone help me here?>>
First of all, in respecting to all great DEVs, I have NO intention to blame anyone else but myself. (I did this to my own watch!)
Second, I have been rooting Android since Cupcake day, so I am not a Noob... (or so I think...) I am very familiar with ADB/fastboot... and use almost daily.
So here is the guide to brick. If Anyone have any idea please help me out!
--------------------------------------------------------------------------------------------------
1st, I tried to use this tool to root+TWRP+scurity patch http://forum.xda-developers.com/showthread.php?t=2713183&page=2 knowing it's NOT tested against 1/8/2100. I just tried anyway... The script went with a lot of errors, it seems the script cannot locate correct files but still push the security patched files into the /system/app (and other places).
I turn on the watch, but it just stuck at boot logo (the orange "Truesmart" logo without animation)
Also, the Recovery is still stock, TWRP is no where to be seen.
Since ADB still works, I adb reboot couple times, pull the battery, let the watch run for 2hrs, etc... Nothing works. The watch just stuck at the boot logo.
Than I follow this thread http://forum.xda-developers.com/showthread.php?t=2641261 and http://forum.xda-developers.com/showthread.php?t=2641261 with Stock firmware downloaded from http://d-h.st/users/Lokifish Marz/?fld_id=30814#files (Omate_1-8_2100_TrueSmart_20140328.zip)
I installed all drivers, restarts my Win 7 (x86) pc (several times), and after several attempts the Flashtool just flash in the Firmware.
The Tools flash with a green Check mark, indicating everything is ok!
However the watch just become a brick after this....
Than this completed the brick process! Now the watch won't even turn on, when I try to use Flash tool again, it always say S_FT_ENABLE_DRAM_FAIL. Google this and you find it's due to flashing wrong F/W, but I don't know where went wrong!
Anyone else have same problem or it's just me? Anyone have solution?
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
funky0308 said:
You said everything...
You made mistake but that shouldn't be problem.
You soft brick it using wrong recovery image and root tool but as you said, you had adb and fastboot on - so if you know what are you doing and I see you know (except of that pary of flashing something that's not for your device .) you should be able to flash stock firmware back.
If you can flash another firmware, try with other firmware...
Don't know what else to say....
Omate build piece of sh*t and we'll all have problems with it...
It's very hard to differentiate devices.
All of them has same nr on mother boards and, as I said, we will all have problems with Omate and their TrueSh*t...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Ha! Very true! I think you are right! I believe Omate have many segmentation on their HW/SW, even with same model number.... A lot of things changes between versions which makes the "factory image" not compatible....
Anyone has the latest (4th list) 1/8/2100 TS who could dump their whole image for me would be helpful...
I would like to help you but mine is 2nd list and it's still on customs office...
Omate shipment experts, you just gotta love them....
Sent from my C6903 using Tapatalk
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Lokifish Marz said:
Not sure what to tell you on this. A board revision change is possible as the Omate_1-8_2100_TrueSmart_20140328.zip was from a 1/8 2100. I can't even test stuff anymore as I gave one to a tech student that's studying network and system security and the other four were stripped down, reworked into data gathering modules and then donated to near space projects.
Click to expand...
Click to collapse
Thanks Lokifish for your comment... Is there anyway to get a latest F/W? If you know anyone I could contact, please PM me... Thanks!
Anyone have yet received a 1/8/2100 on 4th list could PM me a Factory F/W dump?
I tried another XP PC with all steps checked and rechecked but still... No luck...
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
cheahcl said:
Teach me how to do a dump and I'll dump it for you. I was also looking how to backup my stock firmware before playing around, seeing as no one has our version of firmware uploaded for restore yet.
Also received mine yesterday and firmware version is 20140513, pretty damn recent.
Click to expand...
Click to collapse
Thanks a lot! First of all, Currently don't do anything posted on XDA yet since most of them will not work with this version of TS... (This is where I am now...)
First of all, please get all necessary tools directly from this post "All Tools" http://forum.xda-developers.com/showthread.php?t=2734687 (Do NOT download or install any other things there!)
Follow those steps: (modified from link above)
1. Download "All Tools"
2. Install Universal ADB Drivers (included in All Tools) <--If you already have ADB up and running, it's not necessarily, then.
3. Enable USB Debugging on watch
4. Launch MTKDroid Tools
5. Connect watch to PC
6. Please follow the instruction from here: http://www.chinaphonearena.com/foru...up-MTK6592-MTK6589-MTK6577-and-all-MTK-Phones
a. Skip everything above and just starts from "B) Open ADB prompt to begin communication with the phone" .
b. Don't worry about the recovery thing... TS comes with a recovery which is not locked and you can do everything this article said with only stock recovery. (also no busy box is needed, nor su since TS run everything in root!)
c. You could also refer to the video guide below for details
7. it's okay to just provide the file you got after finishing the step "C) Read back the ROM with MTK Droid Tools" I should be able to do the Step D) and after myself.
Thanks a lot for your help!
Lokifish Marz said:
You guys are going to have to help each other out on this one. I've already deleted 90% of any and all Android dev stuff from my personal file server and computer. This includes tools, guides and work going as far back as the original HTC Evo.
Click to expand...
Click to collapse
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
ok will get it to tonight. about 6 hours time. cheers
lssong99 said:
Dear Lokifish,
Could you please still keep those tools on the host servers so people can still access them? (Like "All tools", etc.) Please...... (I need a emoticon of a small kitten with big eyes here...)
Thanks!
Click to expand...
Click to collapse
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Lokifish Marz said:
The space was given to me for free as a recognized developer and contributor. Seeing that I have left development completely, it is not right that I continue to use the services. So at the end of the week the files will be purged and I will ask the xda remove my developer and contributor status.
Click to expand...
Click to collapse
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
lssong99 said:
Oh! I see the situation... In this case, may I have your permission to host those files somewhere (maybe by XDA moderator, or ...me?) so they could still be accessible?
I could feel your feeling on this fiasco. Must be quite frustrate experiences for you...
Click to expand...
Click to collapse
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
cheahcl said:
https://dl.dropboxusercontent.com/u/25414599/!Files_to_FlashTool.rar
I've done step D as well, good to just flash it I guess.
Let me know if it worked, before I start messing about. I'm not good in all these stuff. Been flashing since HD2 days but still, just a tutorial follower, can probably count Linux commands I know with 1 hand.
Click to expand...
Click to collapse
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
lssong99 said:
Dear cheahcl,
Thank you soooo much for the image! I successfully restored my TS and now EVERYTHING GOES BACK TO NORMAL!
If you want to play around, please don't forge to back up your IMEI! since the MTK SP_Flash_Tool will wipe your IMEI!
Please follow this guide here: http://forum.xda-developers.com/showthread.php?t=2631953 under "IMEI Backup Procedure" before proceed anything dangerous!
After this, you are good to go! MTK is non-brickable (from what I learned for the past day... All you need is a corrected factory F/W!)
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!!
Click to expand...
Click to collapse
don't sweat it, haha i needed to backup my original firmware as well anyways, seeing how scarce it is around here and all the weird discrepancies in HW/SW versions. good to know i can always fall back on this file. haha yeah i've also backed up my imei. time to play around and see.
cheers
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Spoetnicus said:
Ive managed to get my brand new watch stuck in a bootloop after using framaRoot to root it. (I know, I know)
Now, I am able to boot into recovery mode or factory, and tried a factory reset. No luck, so i'm pretty sure the issue is in the /system partition.
Does anyone know if there are zip files somewhere that i can flash from recovery, to restore the system partition?
Device:
- 1GB / 8GB / 2100MHz Version
- Originally unrooted
- OUI 2.1
- Modem Ver: MOLY.WR8.W1315.MD.WG.MP.V4, 2013/08/14 18:16
- No other modifications besides the rooting (which did work already before I rebooted)
Click to expand...
Click to collapse
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
lssong99 said:
The TS (or any MTK based system) does not use the usually "recovery backup/restore" way we familiar of, instead it goes the "special tool on PC backup/restore" method. You need ask people who receive their watch in around the same time as yours with same configuration to backup their watch FW with MTK tools than restore with said FW.
Basically what I had done in this thread!
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Sent from my HTC_One_max using XDA Premium HD app
Click to expand...
Click to collapse
Thanks!
Im pretty sure that I was on 'Omate_TrueSmart_20140513.103530_V2.0' before I bricked it, so that gives hope
I dont have it with me right now, but Ill try it as soon as I get back home on monday
Thanks again for the tutorials and reply
lssong99 said:
Please follow my another guild to see how to do this...
http://forum.xda-developers.com/showthread.php?t=2758733
Click to expand...
Click to collapse
HEY! It worked
I'm back at a functional Truesmart
Thank you soo much
And in case three smiley's aren't enough:
Also, quick note for other people bricking their phone, my issue (after I bricked it again), was that I used an app to change the density property, which broke the boot of the watch.
The app that broke my watch was: https://play.google.com/store/apps/details?id=com.birdapi.android.dpi
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
PariahNine said:
As the title states, I have an HDX 7 currently sitting with an older firmware and Safestrap 3.70 (TWRP v2.6.3.1).
I haven't touched anything on it since February 2014. My daughter has been using it primarily, but she finally got her own tablet, so I'm reclaiming this one.
Currently, I frequently get a blue screen followed by the tablet rebooting when attempting to watch YouTube videos via the app. Further, I have to uninstall all updates to Google Play for it function at all.
As I recall I also modified some system file to prevent Amazon OTA updates.
I'd like to get this device caught up in terms of current trends. If someone could direct me to my best options and perhaps a guide, I'd really appreciate it. Much of what I'm seeing is for later firmware versions.
Also, if there is a method to retain root and recover the extra storage used by Safestrap, that would be ideal.
Thanks in advance!
Click to expand...
Click to collapse
Given your firmware level:
- verify device is still rooted (use towelroot if needed)
- flash twrp recovery
- update bootloader to v3.2.3.2
- unlock bootloader (try 1-click method)
- flash rom of choice (Nexus, CM 11/12/13), SlimLP)
Search through the forums for relevant threads. Ask questions along the way. You have some work ahead (hours) but a nice reward at the other end.
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
PariahNine said:
Is there anything special I need to do to remove Safestrap? I forgot to mention I deleted all of the other rom backups on the device and moved the rooted rom to the default slot to free up space. Pretty sure I have the original rom backed up on my desktop. Do I need to revert before doing any of the above?
Click to expand...
Click to collapse
Thoughts:
- moving roms between slots (specifically stock) via backup/restore is generally a bad idea in Safestrap; consider yourself lucky if you used this technique
- if the rom in the stock slot (assuming FireOS 13.3.1.0) boots properly then you can safely remove Safestrap v3 via the uninstall option in the apk
- do not wipe anything in Safestrap nor execute a 'factory reset' from the native Kindle recovery menu (bad outcomes)
- keep WiFi off / airplane mode engaged unless you are 100% sure the OTA block is working
- snag a copy of Flashify to install twrp and the 3.2.3 bootloader update
- check MD5 checksums with ES File Explorer or another tool before flashing; especially important for bootloader update!
- backup your existing recovery with Flashify before flashing twrp; leave a copy on the device
- enable USB debugging in Kindle settings (optional but offers additional recovery options should something go wrong)
- flash twrp first and make sure it works (reboot to recovery; have a look around but don't change anything)
- reboot FireOS and then use Flashify to update bootloader. Did I mention you should check MD5?
Post when above tasks are complete or if you have questions. Cover bootloader unlock next. Be aware the above steps carry some risk including permanently bricking the device. Make sure you have a clear understand on what is suppose to happen; double/triple check everything before committing changes. Good luck.
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
PariahNine said:
So, I understand everything above other than uninstalling Safestrap via the .apk. Is this accomplished via the original apk I installed Safestrap with, or something separate. Also, will I lose root by uninstalling Safestrap?
Click to expand...
Click to collapse
- use the original apk to remove (uninstall) Safestrap v3 recovery; you do not need to uninstall the apk itself
- uninstalling Safestrap will not impact root
---------- Post added at 10:37 AM ---------- Previous post was at 10:30 AM ----------
PariahNine said:
Ignore the previous post. I've successfully uninstalled Safestrap and reinstalled TWRP. So far, I've attempted to update the bootloader via both TWRP and Flashify, but it's still showing 13.3.1.0 under the device information\system updates. Could this be due to whatever modification I made a couple years ago to prevent OTA updates?
Click to expand...
Click to collapse
The FireOS version number will not change following bootloader update. It is a separate 'component' whose version can not be independently queried or verified. Typically the system (what you see, ie: FireOS) and bootloader are updated together and share the same version identifier. In this instance are only flashing the bookloader update as FireOS will soon be replaced by a different ROM. No need to update it and assume the associated risks.
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
PariahNine said:
Ahh, gotcha. Problem I'm having now is getting the bootloader unlocked. I downloaded the 1-click file, ran the batch file, and Virtual Box was installed. Once it finished installing it opened up and showed two instances of 1-click, but then nothing happens in either Virtual Box or the cmd window opened by the batch file. If I double click on either instance of 1-click, the last line says it's loading the kernel, but it stays that indefinitely. I attempted closing out Virtual Box multiple times, reran the batch file, all with the same results, sans the installation of course.
Click to expand...
Click to collapse
Hum. Best handled by @draxie who developed 1-click. Generally pretty responsive to forum posts. If 1-click doesn't do it can always try the manual approach (a LOT more involved but not risky). Let's see what shakes out.
This is what I'm getting from the batch cmd window:
VirtualBox does not appear to be installed
Downloading 'https://www.virtualbox.org/wiki/Downloads' to 'C:\Users\Pariah\Down
loads\1-Click\1-Click\dwnlds'
Download complete.
Downloading 'http://download.virtualbox.org/virtualbox/5.0.12/VirtualBox-5.0.12-
104815-Win.exe' to 'C:\Users\Pariah\Downloads\1-Click\1-Click\VirtualBox-5.0.12-
104815-Win.exe'
Download complete.
Launching the VirtualBox installer momentarily
Please complete the installation with USB support enabled
Installation complete.
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Virtual machine '1-Click' is created and registered.
UUID: 6b44be97-c931-47a5-8eeb-b780f5783b78
Settings file: 'C:\Users\Pariah\VirtualBox VMs\1-Click\1-Click.vbox'
VBoxHeadless: supR3HardenedScreenImage/LdrLoadDll: rc=Unknown Status -23021 (0xf
fffa613) fImage=1 fProtect=0x0 fAccess=0x0 \Device\HarddiskVolume2\Windows\Syste
m32\acaptuser64.dll: None of the 1 path(s) have a trust anchor.: \Device\Harddis
kVolume2\Windows\System32\acaptuser64.dll
VBoxHeadless: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Windows\system32\ac
aptuser64.dll': rcNt=0xc0000190
Oracle VM VirtualBox Headless Interface 5.0.12
(C) 2008-2015 Oracle Corporation
All rights reserved.
Click to expand...
Click to collapse
And the 1-click instance in Virtual Box is showing "Booting the kernel."
Here is the method I used to block OTA updates.
Originally Posted by berndt_toast
Yeah, I agree. Staying rooted is difficult, but doable. I am still on the rootable version (13.3.1.0) and have stayed on it even through the OTA updates that have been released. I have stopped them from auto-applying (and from even being seen as updates) by doing the following:
I renamed otacerts.zip to otacerts.zip.old in /etc/security/
I also renamed com.amazon.dcp.apk to com.amazon.dcp.apk.old in /system/app/
Doing those prevent OTA updates from working and if you check for updates from the device, it says none are found (at least it has worked for me).
Click to expand...
Click to collapse
Do I need to undo this before proceeding with the bootloader update and unlocking?
PariahNine said:
Here is the method I used to block OTA updates.
Do I need to undo this before proceeding with the bootloader update and unlocking?
Click to expand...
Click to collapse
No - tasks ahead have no dependence on Amazon's update engine.
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
PariahNine said:
10-4. I attempted to find the manual method for unlocking the bootloader with no success. Not sure if I'm looking in the wrong section of the forum, or just overlooking it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
EncryptedCurse said:
http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281
http://forum.xda-developers.com/kin...tools-create-unlock-img-fix-boot-img-t3050689
You're going to need a Linux.
Click to expand...
Click to collapse
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Davey126 said:
Can be accomplished from Windows but a royal PiTA to get the drivers right. Tough having to hold but you probably want to wait on @draxie unless you are very comfortable with device manager and working around unsigned drivers on Win 8/10.
Click to expand...
Click to collapse
PariahNine said:
I'm actually running Windows 7 64; not sure if that matters. Perhaps why 1-click isn't working?
I'm trying to get Minimal ADB and Fastboot to work, but while my HDX is being detected while booted into the OS or TWRP, it's not in Fastboot mode for whatever reason. I've cleared out the old ADB drivers and reloaded them after plugging the HDX into a USB while in Fastboot mode, and still nothing. It's not showing up under 'adb devices' or 'adb fasboot'.
Click to expand...
Click to collapse
Davey126 said:
Yup - that's the driver issue I referenced. Recommend waiting for response from 1-click developer before diving in. Win 7 x64 not an issue.
Click to expand...
Click to collapse
If you want to give manual unlocking a try:
- use these drivers; you likely need to reinstall when flipping between adb and fastboot
- detail procedure
- suggest browsing this thread for additional info/tips. Lots of noise but some diamonds in the rough too
- careful not to go down a rabbit hole; some solutions are one offs that worked great for the poster due to their familiarity with a particular too, platform or technique
- unlike almost everything else with HDX you can not harm your device with bootloader unlock attempts. It will either work or not with no adverse consequences either way
There are a few excellent posts by @Cl4ncy, @jerryl and others (possibly one of mine) in different threads; unfortunately I wasn't able to surface them in a quick search. Nature of the HDX forums. A gold mine if information that is a bxxtch to access.
Before diving in you may want to flash CM11 or Nexus v4 which can be done with a locked bootloader. Both are rock solid KitKat based roms that will expose the full capabilities of your device and offer continuity to CM13 once unlocked.
Good luck.
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
PariahNine said:
First off, I wanna extend a heartfelt thank you to @Davey126 for basically holding my hand through much of the process, and @EncryptedCurse for offering insight as well; folks like you are the reason I've been apart of this community for several years and always come to first when I'm looking for solutions revolving around Android products.
Secondly, I'd like to share a couple of my experiences as a novice that may have others in the future. For whatever reason, I couldn't get 1-click to work on either of my Windows 7 machines with two totally different installations; one being Windows 7 Professional 64-bit, and the other being Windows Home Premium 32-bit. Ultimately I ended up upgrading my system to Windows 10 and was able to unlock the bootloader without any difficulty at all. With the fresh upgrade to Windows 10, I simply uninstalled VirtualBox and reran the 1-click batch file. One thing that should be noted is that there's no reason to click the box to run VirtualBox at the end of the installation process, and may be something that contributed to my confusion and the confusion of others. Secondly, a window for PuttyTel should open up after VirtualBox is finished installing, and the PuttyTel window is where all of the "magic" takes place. I didn't find any of these distinctions in any of the numerous posts I scoured through, though I may have overlooked them.
Either way, thanks again to the three of you... now I just gotta figure out which ROM I'm gonna slap on this bad boy. Been waiting nearly 2 years for this moment.
Click to expand...
Click to collapse
Happy to hear you were sucesfull. Thanks also for sharing your experiences and insights. Should be helpful to others as they navigate through the process. Every nugget of new information helps!