Related
I'm thinking of creating a small archive of files, that when extracted to the SD card root, and applied, will root the phone and apply a firmware in only three steps.
It will only contain four files - the RC29 DREAIMG.nbh file necessary for downgrading, an update.zip that contains the latest SPL and Radio, the latest Cyanogen Recovery image, and a simple script that applies root, SPL/Radio, and your favorite firmware.
I'm not sure if it will work, but constructive criticism and ideas are welcome.
_______________________________________
First method: Root from SD card
This method puts all the necessary files on an SD card, and does not require a computer after that.
Basically, in a zip file, you have the RC29 DREAIMG.nbh, update.zip, and root script.
You extract this to the root of a FAT32-formatted SD card.
You reboot with camera+power, apply the DREAIMG.nbh, reboot.
Once the phone is booted, type in "sh /sdcard/root.sh".
From the exposed root terminal, it will begin the following:
Write the Cyanogen recovery image to flash, move image to system/recovery.img, remove image file
Place commands in /cache for recovery to apply the radio/spl combo package and if it exists, a custom firmware, in the correct order
reboot recovery, performing the above tasks automatically.
Benefits include:
- No telnet app required, not opening up a telnetd, more secure
- Only one command to enter
- No(?) risk on flashing the Hero-compatible radio/SPL out of order and bricking that way, as both are flashed at the same time
- Automates several of the processes in rooting, allowing for a quicker root
- Can be placed on a special "rootkit" sdcard, and used to quickly root your friend's phone in a matter of minutes, anywhere
_______________________________________
Second method: Root from PC
Another method I thought of uses no manual copying to the sdcard, but requires a PC with fastboot(?) and adb.
First, it pushes the RC29 DREAIMG.nbh to the sdcard, and issues a reboot to bootloader.
You press a few keys to write the image, and reboot.
--OR--
First, it pushes an update.zip containing the update just before T-Mobile patched the root kernel exploit, then it puts the commands to flash it and reboots into recovery. After that flashes, it reboots again.
From this point on, it's all automatic.
The script waits for the device to be ready, and adb install's the auto-root exploit apk, and launches the intent through adb shell am start [...]
At this point, the WiFi settings are probably not capable of downloading the Cyan recovery in the case of those of us without data plans, so it will need to be pushed.
Once the autoroot apk flashes the recovery, we must write parameters to flash the radio/spl combo package, and the custom firmware (if applicable), to /cache, and reboot.
At this point, the radio, SPL, and firmware should be pushed and written, so the script exits.
_______________________________________
If this sounds stupid, doesn't make sense, will auto-brick your phones, start global thermonuclear war, make all random numbers generated by your phone divisible by three, cause your meticulously placed lineup of G1 dominoes to collapse prematurely, or boot up the LHC and wind up creating a black hole, I am terribly sorry, but it's an idea I had at 2 in the morning, and it took me this time to research some things and write this post. It's about 5:30 AM now.
This is only an experimental concept. Some things might not be completely thought out. I'm tired, and hungry. I may create a proof-of-concept implementation of this, if I knew a bit more about the syntax of describing intents to launch in 'am', or the command syntax of the package:/META-INF/com/google/android/update-script file.
dont forget that for root from SDcard, EU users need a goldcard, so its still not that easy..
even for insta root from PC, you still need to downgrade, and for that we'll need a goldcard.
why not just use 1click root?
First you have one click root which does give you access to recovery with security off so possible to somehow go from there instead of downgrading and all that hassle. I personally to do not care to see the advancement of this app for the simple fact that there are already a wave of people that can not read and expect hand holding every second of the way and you want to make it even easier to confundle their minds.............are you nuts....
I already have a rooting sdcard for rooting other people's phone that contains one click recovery flasher, cyan 4.04 and the hard spl and it takes me 10 mins to do it just cause off the first boot up takes so long
also you cant have your pc reading the sdcard at the same time that the phone is
The concept is good but...theres many complications to have it done automatically.
I sure would like to see something like this. I have a G1 that I rooted the long way and a MT3G rooted with the one click method. I have enough knowledge to follow instructions and read, I partitioned my own card, so the G1 was doable. I dont have the time or the knowledge to go the long route with the MyTouch gold card ADB route and would love to be able to flash Hero ROMS when I get the bug. I have Cyan's latest on the MT now and its awesome like all his stuff but I would have played with Drizzy's ROMs. For someone like me with a little ability but far less than most people on here, something like this would be the bomb!
not sure if its possible or anything, but there should be some way for the script to check if the phone has a pvt board or not, and if not, it prevents the new spl from being flashed, should reduce noob bricks.
Leave root the way it is I think the harder it is to root your phone the less peaple are going to do it. I spent alot of time reading before I rooted, not so much to learn how to do it, but to decide if I wanted to make the jump. During this reading process I learned the ways of XDA, use search, where to place the right questions and where NOT to and finally read first then ask. With an autonatic root I would have loaded it then freaked out if something went wrong and started posting root questions all over the place. Leave well enough alone... Learning to root give you the right to pursue other adventures.
maybeoneday said:
Leave root the way it is I think the harder it is to root your phone the less peaple are going to do it.
Click to expand...
Click to collapse
Frankly, I didn't root my phone to feel special, so I don't see any benefit whatsoever in less people doing it.
I don't think this will work though. There's too many variables. As described it will only root US phones. UK phones would need RC7, so you'd have to include both and check if the current OS is CRC1 or CRC37 (or respective older/newer versions). But European phones outside the UK (like my German G1) will be on CRC37 too, and those won't take RC7 without a goldcard, so you'd have to automate goldcard creation as well. I'm sure the complications don't end here.
Also, shoving Haykuro's SPL onto inexperienced/unsuspecting/ignorant users' devices is just begging for trouble. Just use HardSPL - the rooting kit won't be able to run Hero-ROMs right away, but at least that won't brick the phone if flashing some rom downgrades the radio. (E.g., I know some official updates do that.)
1 click root is so simple and idiot proof (and im a total panzy noob lol)
i don t think there is any simpler way to do this lol
Frenchtom, nothing is idiot proof, have you been over to the q and a section, if there is a way to do something and good instructions, it will get screwed up cause of people not taking the time to read the complete directions and then read them twice to make sure they comprehend them
Okay, thanks for your input, everybody.
I did know about 1-click root, however I thought that depended on a kernel vulnerability that was already patched in the OTAs. I was looking at a more universal(ish) method, and I did not know about the "goldcard" issue. I did know that UK phones would need RC9, but I failed to include that as I really just wanted to get to bed.
Also, I don't think that root is anything "special", i.e. some sort of elitist egotist symbol that says "I haz root fone and I better than u". Seriously, more people should be allowed to use the more advanced features of their device at their own choosing, knowing that there are risks involved.
People who walk up to someone, say "I got a root phone", shows off some massive demo of awesomeness (i.e. Hero), and doesn't teach others to root the G1 themselves (or worse, charges for instructions that could be found free here) are really the antithesis of an open-minded community of developers adding more features as they feel, for what little donation money they get and the credit of doing something cool for other G1 users.
I do however agree that pushing features that can potentially insta-kill the device on the average person and their grandma, people that wouldn't know what the benefits of root are, and people who would never even have known that their G1 ran Linux (or what Linux is, for that matter), is just asking for trouble. A fair balance between educating people about the phone's internals and making easy-to-install root packages and stuff should be kept.
I learned a lot about Windows Mobile and embedded software when I first flashed a custom ROM to my HTC Wizard years ago. And I actually had a fear that if any small detail were left out, or if I breathed on the phone the wrong way, the flash would fail, white-screen, and brick out.
The G1 is no different, even though the flashing process has come a long way, we still have an IPL, SPL, bootloader mode, many different variations, board revisions, regional changes and operator customizations/lockdowns (I had a Cingular 8125 G3 btw), and many versions of Consumer, Engineering, and HardSPL that have to be treated very, very carefully, just like on the Wiz.
Anyway, anyone's free to try and build a better mousetra--- err, rootkit using my ideas. And thanks plenty to the dedicated developers here, the more enlightened users for helping me find out why this wouldn't work, all the users, without whom, we wouldn't have a reason to develop, and the 17%-or-so of you that dislike my idea.
When I learn a bit more, I might get into making something useful for Android.
repack dreamimg.nbh with everything, so one just has to flash the one image
Oh I am not saying that I think I am special just cause I have a rooted phone, I am also a person that is on here always trying to help walk someone through any issues that may arise,just saying making easier for people to break something because they did not read the instructions is quite common and think that it should take a little bit of work so that you learn in the process
I recently had a problem on my LG vortex. I had rooted and deleted some bloatware, then because I was upgrading phones, I thought I might sell my vortex for cash. So I did a factory reset. Much to my dismay I shortly found out that I had accidentally deleted the home screen from the phones factory memory leaving me in a boot loop. even a hard reset using default recovery wasn't working. After a day or so of research I found a couple of guides:
LG vortex downgrade guide - many thanks to Salem, as much of my guide is copied from his
http://forum.xda-developers.com/showthread.php?t=883314
after a bit of tweaking I was able to recover the phone by following these steps:
Disclaimer: I am not responsible for *any* loss or damage (including bricking) to your device -- use this guide at your own risk!
[Setting up your computer]
if you previously downgraded your LG vortex from 2.2.1 to 2.2 chances are good this part is already done
1. download files from following links:
factory flashing software & firmware
optional free un-rar software
2. plug in your phone (even in it's crippled state) it should autorun, and install some USB drivers
3. extract LGNPST.rar and run the LGNPST_General_v1.2_Lab_Version.msi this will setup to the directory C:\LG Electronics
4. copy/move LGNPST.exe to C:\LG Electronics
5. extract the LGNPST_Components rar file, this will make a directory with two MSI files in it - run these.
6. Go to C:/LG Electronics/LGNPST/ and create a folder called “Model”. Inside that folder, create another folder called “LGVS660″.
7. Extract LGVS660.rar. Inside this, you’ll find a VRZ folder. There are three files inside this: a .tot file, a .scr file, and a .dll file. Move these all into C:/LG Electronics/LGNPST/Model/LGVS660/ (the folder you just made.
8. If you’re on Windows XP, hit start, click on “Run”, and run this:
regsvr32 "C:\LG Electronics\LGNPST\Model\LGVS660\VS660.dll"
If you’re on Windows Vistas or 7, hit start, type cmd.exe, right click on cmd.exe when it comes up in the search area, and run it as an administrator. Type in the following and hit enter:
regsvr32 "C:\LG Electronics\LGNPST\Model\LGVS660\VS660.dll"
[setup complete] your computer should now be ready to fix your phone
Contrary to popular opinion on the many forums I perused researching this, I found that this software does *NOT* require your phone to be in debugging mode! it will see your phone if you simply plug it in at this point
[Flashing the phone]
1. go to C:\LG Electronics
2. run lgnpst.exe
3. if you haven't already boot phone and connect USB if the phone was already connected disconnect and reconnect it to make sure the software recognizes it.
Warning! do not disconnect your phone from the cable under ANY circumstances until the software tells you it's safe to do so!
4. try to directly flash phone back to factory. This will require you to select the .tot file from above under where the program is expecting a .bin file (you'll have to manually type in a filter in your file selection box) also select the .scr file in that same directory.
5. if that doesn't work go to the Data menu
6. select 'data recovery'
7. let that work it's magic and it should transfer to 'emergency mode'
8. select the .tot file and then the DLL for your phone
9. flash -- if everything works out your phone will reboot around 60% with everything on it
10. once the phone has booted completely go to menu and set phone to USB debug to stop the 'flashing' process this will allow you to safely disconnect your phone
ENJOY!!!
[emergency flashing]
*WARNING! the following methods are untested! above methods worked for my phone!*
Once again, do not disconnect the phone under ANY circumstances until the software tells you it's okay to do so!!
1. boot the phone in emergency mode by holding volume *up* and the back button at the same time (as I gather from the above mentioned xda post)
2. once in emergency mode it should be safe to continue from step 8. above.
[end guide]
Many thanks to those out there who helped me build this guide!! I hope it helps!! Now you should have the freedom to try removing all that bloat ware again. Hopefully, with a bit more discretion this time
In case anyone is wondering -- yes, I'm a n00b, and yes, this guide is for n00bs just like me
Advice?
Can this method be used to return a rooted/hacked/modified phone to FULL factory stock so you can return it for a warranty claim? IE- will it remove clockworkmod, superuser, and any other traces that you messed with the phone? Also, is this for verizon?
I had a lg vortex I had to return recently due to a blown speaker making my calls sound like a kazoo.
I DID root it (using gingerbreak)
I DID run some sketchy root programs like setcpu, wifikiller, root explorer, wifitether, and a few others
I originally ran ROM manager to backup my rom when I first rooted, but it said it installed clockworkmod (selected LG optimus V from the list and it worked) in order to run properly.
I have slowly uninstalled all of the software, used rom manager to restore my first backup, then uninstalled rom manager, installed gingerbreak, unrooted, uninstalled gingerbreak, uninstalled everything, then did factory reset from settings menu.
As of today the phone looks stock. No superuser. No sketchy programs, I'm just not sure if CWM or something else could have survived the factory wipe from the settings menu. I know superuser survives a factory wipe, so I'm not sure if I still have dirty files lying around. If verizon knows I rooted my phone it will cost me $309
Is that good enough? I don't want to return a device that has evidence files on it, but I have no clue if clockworkmod got uninstalled with rom manager or not. I never changed roms, I never knew how to boot into cwm, I don't know if it's still there or not. Advice?
EDIT: You should note that my phone is NOT bricked- the speaker is blown, so there should be no limit to the menus, functions, or software tweaks available which would be needed to fix my situation. Also it should be noted that I am not the type of person who condones returning a bricked phone to get another one- That hurts us all. Unbrick yourself using a thread like this or eat your mistakes.
hi, I recently rooted my phone with gingerbreak and uninstalled some bloatware from verizon. Then I couldn't see the home screen, although I can pulled down the status bar. After following your steps above and at running lgnpst.exe. I got the error message saying: Fail to load the Skin.dll. Do you have any idea? Thanks
been looking for you for three solid weeks!
dude, i've literally tried every posted forum in xda, androidforum, soul, phandroid, etc, downloaded every possible software, updates, utilities, recoveries, firms, and yada, yada, yada, and for the past three weeks i have past this one flippin' thread, over (no lie) 20 or so times. and please believe that your solution/explanation for this problem was really my last @#$#@## time i was going to EVER, and i mean EVER, download, install, re-install, re-name, re-write, place, copy/paste, throw-up, stroke, stomp-feet, and dosie-doe anything technology-based/wired-wireless eqipment in this young mans life again!!! so i thank you:victory::victory::victory::victory::victory::victory::victory::victory::victory::victory: and to ALL those not mentioned here (my apologies, but are still and forever will be in my prayers) for this and every single solution/explanations, that has ever been posted for dumb-a#$es like me. and for donating im trying to do that but recently messed up by using google's new/terrible wallet proccess. yes i know i should have used "PAY-PAL" but had already had money link to that GOD-aweful--theivery account. and for all those out there like me/us i will be posting my own thread/solution to this very same problem using my own words in a more in-depth description including all-props to you and for them not mentioned here (my apologies, but are still and forever will be in my prayers). thanks to you all and fyi im stopping here, oh no, i too, will become a master of all this hacking stuff, or i will become a master of destroying them all and then will have new problems for ya'll real hackers to nibble on.!!!
Hi
I am trying to install the Jellybean 4.1.1 ROM on my rooted Nexus S.
The history of my attempts so far are here: Rooted Nexus S OTA Upgrade to 4.1 http://forum.xda-developers.com/showthread.php?t=1833420
I have downloaded the "image-soju-jro03e.zip" form the Android open source website, and used the Nexus Root Toolkit to install it.
This failed, and I attempted to install the image using ROM Manager.
This also failed, and produced a lengthy Recovery Log.
I have read through it and it seems to be telling me that certain files or folders are missing from the download.
e.g can't open /dev/tty0: No such file or directory
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
can't find /sd-ext in /etc/fstab
Is that what this means?
How can I correct it?
The full log is here: https://docs.google.com/document/d/1HWeYsXPnppQbgoloz72RH81E8a479LBmvYXIlzYPETo/edit
S
Help with recovery log
Hello?
Can anyone help me to understand this recovery log?
Should I direct my question to the "ROM Manager" people?
I have tried without success to install JB 4.1.1 from the Google Android Images page, and I think it must because something is missing from the file structure of my current ROM.
Am I on the right track?
M S
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
new hope
nightsky87 said:
First of all, what variant of the Nexus S do you have? If you turn off the device and remove the battery, it should be on the sticker showing the device serial number.
Once you find that, you can head over to this link and look for the right image for your device:
http://www.randomphantasmagoria.com/firmware/nexus-s/
I'm assuming that since you're from 4.0.4, you just need to flash the update zip. If you're device is rooted, chances are you have ClockworkMod installed. If so, maybe you should just consider putting in a custom ROM. Flashing it should be much faster. I'd be glad to help you if you can give more info on your variant, current software state (version, rooted/not rooted, etc).
Click to expand...
Click to collapse
Hello nightsky ( is that like, "nice guy",?) thanks for taking a look.
My phone is a Nexus S i9020, no suffix.
It is running Andriod 4.0.4 ICS. It is "rooted" and "unlocked".
I have Clockwork Mod v.6.0.1.0. Superuser v.3.1.3. and ROM Manager v.5.0.2.0.
I have tried over and over again without success to upgrade to JB 4.1.1 and I am getting sick and tired of this stupid game.
I would be happy to just stick with ICS 4.0.4, but every week, the phone tells me that an "update is available", and I have to dismiss the message every time I look at the phone! When I tried to apply the update It used to crash, requiring a battery-pull reset. Now I have CWM it takes over and says "failed to verify file signature", "install untrusted package?"
If I press on and install, it fails and the android is on its back with a red triangle on its belly.
If you look at the posts I have linked to, I have been on a steep learning curve regarding ROM flashing, and I understand the basic idea, its just that when I follow the instructions given on the forum, It doesn't happen that way for me and I suspect that there is something wrong with the file structure on my phone. That is why I have posted the link to my recovery log.
If you can help, please reply.
I have had a look at the "Random Phantasmogoria" site that you recommend, is it offering anything different than the Google developers site https://developers.google.com/android/nexus/images that I have downlooaded my image from?
MS
another version!
PS I have just had a look at the Google Dev. site and there appears to be a new version of 4.1.1 called JRO03L.
My next attempt, I'll try that.
MS
goodnight
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
jus to add on the post above. the instruction to install the factory images are on the same page where you downloaded the image in question.
and there is something to be wary of : flashing the factory image will WIPE the phone CLEAN (except what's on the usb storage o/c).
albundy2010 said:
Factory images are not to be installed with ROM manager/recovery.
They are factory images that are installed with fastboot.
Your solution is a rather simple but may seem complex to you at first. If that makes sense.
First screw all those one click/ ROM manager crap.
Either download the SDK and get the platform tools add on ( quides are all the over the place). Or use one of those zips people make that include fastboot.exe and a driver or whatnot.
Boot the phone into the bootloader. Connect it to the PC. Open a command prompt in the directory with fastboot.exe and the factory images....
Type in fastboot devices. If your serial comes up just follow the commands in the quide. Re root if you want.
What you where attempting to do reminds me of kids in the arcades just smashing buttons and hoping something works
I am not going to right a guide m. There are stickies and somebody actually made a very noon friendly explanation the other day on here somewhere. Sorry don't know where at the moment.
If there is a specific part or something in particular you don't get let me / us know.
Moral of the story is a once a computer is set up with fastboot properly it is very simple.
Click to expand...
Click to collapse
Smashing buttons and hoping something works?
That's not very nice, or fair!
If you take the trouble to read my post, and the linked previous posts, you will see that I am trying my best to follow the instructions given on this forum, where I hoped to find knowledgeable professionals who contribute their valuable time free of charge to help noobs like me.
So far I have followed the instructions, only to get something other than the result described. This is why I am asking for your help to understand the recovery log, so that I can work out for myself what went wrong, and what I should change next time to get it right.
At this point in the journey I am still unsure about backup. I have "backed up" using the nexus root tool kit, which is a Nandroid back up, and I have "backed up" using ROM manager, but Titanium Back-Up does not recognise the backups and wants me to "back up" some more. After all this is over will I be able to clear out all the dross that my phone memory is accruing? Is there any point backing up Apps like "Google Earth" when I can easily download them from the Play Store after I have my new OS? etc... etc...
Anyway, I am going to try again, this time with the new JRO03L image, and this time I shall do it Command Line style instead of the "one click crap", as you recommend, my friend. I'll let you know how I get on.
MS
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
adam_4049 said:
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
Click to expand...
Click to collapse
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
C-Lang said:
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
Click to expand...
Click to collapse
i did do a search and nothing has been able to help me so far. i also did read that it is device specific but have also read it has worked for some people. unfortunatley in australia we do no have any microsoft stores so its not that easy to just take it somewhere.
I feel like there are files missing from c drive. Almost like it started to do a restore then stopped halfway. In which I have never been able to get it to that stage for that to be the case.
I did some reading and was able to find the recover partition and tried to run the install.wim file from which I understand to basically be the “OS”. When I try to run it it says “no such interface supported”
From what I understand there is just no way to do a fresh install on these things regardless of what the problem is which is disappointing on Microsoft’s behalf.
C-Lang said:
And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you.
Click to expand...
Click to collapse
No. Those recovery images are device-type specific. Not device-specific. You can safely take one WIM file from the recovery partition of your device and use it to recover a different device of the identical model.
adam_4049
I see that you were able to start a restore process and it fails in the middle.
You may try the following: boot into the command line mode and format the boot partition (probably drive C: ). This would fix the disk errors if they are present, but you'll lose everything. Use diskpart tool to find the disk letter. Be careful with diskpart - do not delete partitions or issue "clean" command.
Then assign the letter to recovery partition with diskpart (say, R: ), then expand WIM file from the recovery partition with the command like this:
Code:
Dism /apply-image /imagefile:R:\RecoveryImage\install.wim /index:1 /ApplyDir:c:\
R:\RecoveryImage\install.wim - a path to install.wim on the recovery partition.
More info: http://technet.microsoft.com/en-us/library/hh824910.aspx - you need only "Dism /apply-image" part, bcdboot is unnecessary. Lets hope that "apply-image" option is present on RT.
This would forcibly expand the WIM file to your disk C:. Or at least you'll be able to see why it fails.
This may help. Or may completely brick the device and you'll need to go to service. So use it on your own risk. And you should be familiar with the command line - so don't ask how to use diskpart.
I had a problem with the recovery process when I've played with BCD and added a boot from VHD option. Had to delete that extra boot setting - and then recovery went fine. But I assume that you have not played with BCD.
Yeah, looks like people dont use search, what you want is a nice useful soul that creates a USB recovery from his EN-UK Surface_RT and puts it up on Copy, or Dropbox or something like that...
(NOTE: this post is a duplicate of a similar thread I started on the Android Central user forum)
Hello everyone,
In the continuing saga of the Leagoo T5C i bought before the holidays from GearBest, I've seen the good (the price and overall build quality, along with a reasonably good user experience), the bad (some notifications that I just can't get rid of, among other things), and I now present you the ugly: after watching a review video on YouTube about my device, I learned that it came loaded with a Trojan called "Gorilla.AM"...
***EDIT: apparently, the Trojan's name could actually be "Guerrilla.AM", I'm not sure.***
Needless to say, I did as the tester had, and installed Malwarebytes, which, sure enough, found the exact same Trojan on my device.
You can watch the video here: https://www.youtube.com/watch?v=R5l3z7BvBtk
It so happens that it's embedded in Leagoo's own application launcher, called Sujet (in French; maybe it's called "Subject" in English, I don't know). I can force quit the application, since I use another launcher called Apex (good pick, by the way), but Malwarebytes can't seem to shake the Trojan off my device nonetheless.
A quick search on Google gives very little in the way of information about this malware, but I'd like to be on the safe side, so I came here.
Any contribution would be welcome at this stage.
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Lannig said:
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Click to expand...
Click to collapse
Hi,
OK, first off, thanks for the reply. Secondly, as I've stated before, I'm new to Android, and though I know my way around the command line in both Windows, Linux et OS X (not so much macOS: my MacBook Pro is 12-years old...), I suppose there are some things to set up first, before you can actually do what you suggest.
I understand that ADB stands for Android Debug Bridge, so is it an existing functionality in, say, Windows, that you can trigger from the command line, or a third-party software you have to install first?
On the Android side, what action should I take? Any Developer command to enable/disable to let ADB interact with my device the way it's supposed to?
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Lannig said:
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Click to expand...
Click to collapse
OK, thanks for the heads-up; I've already installed a Terminal emulator on the phone, so I'm gonna give it a go in a moment. I concur about Phoneandroid, alas: I've just received flak from one of the moderators because I'd double-posted on the same subject, whereas I'd just posted one thread, in the wrong part of the forum, according to him. Go figure...
OK, please feed back on your attempts, both from terminal emulator and through ADB.
Alas, I suspect that root will be required. It was for me on my Z5 and M5 to get rid of Leagoo's crapware.
Phonandroid is a bunch of losers with bloated egos posing as experts when 2/3 of the replies given are total BS.
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
(Additional question, not quite related: Aida64 indicates that my device runs a 4.4.49 version of the Android kernel, when the current version for Android 7.x is supposed to be 4.4.1; how does that compute--no pun intended--with my issue?)
Missing adb command is because the adb.exe (Windows) or adb (Mac) file is not in the command path. Either make the folder that contains the adb[.exe] file the current folder using the cd command or use whatever context menu for opening a command line window within the currently selected folder works, or even add that folder to the PATH variable. Google "add directory to path" for Windows and MacOS.
No idea about the kernel version. Minor kernel versions may vary within an Android release. Not surprising and most definitely unrelated to your problem. The crapware certainly isn't part of the kernel. It's most likely a system app i.e. a folder within either /system/app or /system/priv-app folders. You can't delete it without root, but you might be able to disable (freeze) it with the commands I gave you.
OK, thanks. I did "cd" to the folder where I had unzipped ADB on Windows (on the Mac, when I tried to open the ADB executable, I got a "cpu not supported" error message in the Terminal, as I feared, since my MBP is 32-bit-only, and most Mac applications nowadays only support 64-bit CPUs), and still got the "adb unrecognized command" error in PowerShell.
The phone was plugged in, and the right USB mode, so I'm still a bit baffled here. Gonna try it again with a different approach. Will keep you posted.
Over and out...
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
UglyStuff said:
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
Click to expand...
Click to collapse
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
rhn19 said:
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
Click to expand...
Click to collapse
If you are new to this, use an app from play store for uninstalling and integrating apps.
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
UglyStuff said:
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
Click to expand...
Click to collapse
Jailbreaking vs Rooting is like 5-1 on difficulty level. Because Android is Open source while IOS is not. I would highly suggest you Root it if your phone does not have warranty. After all something that is on /system partition like your launcher will need superuser access to modify it. I cannot think of a way that wont void your warranty.
You can flash TWRP and then boot into aroma-fm but that will void your warranty. Rooting is the preferred option here.
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
UglyStuff said:
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
Click to expand...
Click to collapse
Why do you want a new firmware? I don't get you man, do you want to clear out the malware or try a new ROM? Because i think you would have to build a new ROM, there is not one available i guess.
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
UglyStuff said:
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
Click to expand...
Click to collapse
If you use malwarebytes after root that thing wont happen. And almost all of the OEMs have a trigger which voids when rooting or flashing firmware. After that the OEM wont give you updates unless you use the A/B partitioning system.
OK, I understand how rooting my phone would void the warranty: after all, it's a substantial change in the phone software, and the OEM can't be made responsible for any mishap that occurs after I've rooted the phone.
What's the A/B partitioning system (I suppose it helps partition your storage space)? I don't have a microSD card installed (I use the slot for my second SIM), but I do have 32 Gb of storage space, minus what's already used up.
Do you know KingRoot? Is it as good and (reasonably) safe a rooting tool as they say it is?