Related
I was asked to port my Android Loader for the HD2 so that the HD Mini users could have the same benefits of automating the boot process. The result is this thread and I hope you can benefit from my work.
**PLEASE READ ALL THIS POST BEFORE DOWNLOADING AND INSTALLING THE APP TO AVOID ANY PROBLEMS**
**IF YOU HAVE ANY PROBLEMS PLEASE READ POST2 *HERE* BEFORE POSTING YOUR PROBLEM IN THE THREAD**
--------------------------------------
--------------------------------------
This Android Loader will allow you to do a few things. Firstly you can start Android easily once you are already in Windows. It comes with a cool looking icon in the Start Menu and you can add it to Sense or Mobile Shell or whatever you use as your day to day interface.
INSTALL THIS APP TO DEVICE MEMORY!! DO NOT INSTALL TO STORAGE CARD OR YOU MAY HAVE PROBLEMS!!
After installation you will be asked if you want a dual boot option after you start your phone. If you do then you can set your default Operating System (Android or Windows Mobile), then you will be asked for an AutoBoot timeout (3, 5, 10, 20, 30 or 60 seconds). You will then be asked which Icons you want to be displayed in the Start Menu (Android and Android AFTER a Soft Reset with no prompts). The 'Android with Soft Reset' icon will allow you to boot cleanly into Android straight after Windows Mobile finishes loading if you dont want a Dual Boot option.
Lastly you will be asked to select the Path where your Android files have been copied to. At the moment your Android files are copied to the ROOT of the 'STORAGE CARD' and this is what should be selected, unless they are moved in future Development updates of Android.
If you set up a Dual Boot option then after a soft reset of your phone, as soon as WindowsMobile loads up you will be prompted to choose what you want to boot into. If you make no selection then your default Operating System will be Auto loaded after the time out.
Last but by no means least there is a folder in the Start Menu called 'Android Loader' which holds a Manager app. With this app you can change any of the default settings. There are also 2 switches in this Start Menu Folder. Fast Mode will load Android as soon as the icon is clicked, Safe Mode will always ask for confirmation when the icon is clicked to avoid accidental loading.
When Android loader runs it will run Haret_Photon7227.exe after a 1 second delay which will start Android.
--------------------------------------
--------------------------------------
This app should work with ANY language Rom as a script searches for the correct name of the Storage Card when it is first run. If there are any problems with non WWE Roms then please let me know.
DONT ASK IN THIS THREAD ABOUT QUESTIONS OR PROBLEMS WITH ANDROID. THIS IS TO BE KEPT JUST ABOUT THE ANDROID LOADER.
--------------------------------------
--------------------------------------
Cab Useage:
1. Make sure you have your desired build of Android copied across to your Storage Card BEFORE installing this app.
2. INSTALL THE CAB TO DEVICE MEMORY (IN WINDOWS MOBILE)!! DO NOT INSTALL TO STORAGE CARD!!
3. You will now be asked if you want a prompt everytime you start WindowsMobile to run Android or continue to Windows. This is your Autoboot setting. If you select No then you wont get a prompt after WindowsMobile boots up.
4. You will now be asked which Android links you want displayed in the Start Menu (Android, Android with Soft Reset or Both).
5. You will now be asked select the folder where your Android files are copied to. THIS SHOULD BE SET TO STORAGE CARD (WITH NO SUB FOLDER)!! You only have to do this once, it will remember the settings until you uninstall the program.
NOTE: If your icons dont change in HTC Sense after upgrading the cab then install and run SICC (Sense Icon Cache Clearer) *HERE* and your new icon will be shown after a soft reset.
--------------------------------------
--------------------------------------
I made this as a favour to the HD Mini Community. If you find it useful you do not have to donate if you dont wish to but please hit the THANKS Button to show your appreciation.
Enjoy
Mark.
Problem Solving
To check your Settings you must have a Registry Editor installed on your Phone (free ones can be googled):
Browse to HKLM, Software, MSkipAndroidLoader
Check all the Sub Folders are set correctly
- AndroidFolder: Should be set to \Storage Card (or equivalent for your language),
- AutoTimeout: Duration til AutoBoot (in Seconds),
- BootupOS: Android or WindowsMobile,
- Mode: Fast or Safe,
- StartupOption: Yes or No
-----------------------------------------
-----------------------------------------
Android isn't loading:
Did you copy your Android files to the root of the Storage Card first? Yes
Did you install this app to DEVICE Memory? Yes. Are you Sure? YES.. Are you ABSOLUTELY SURE?? Ok maybe I installed it to Storage Card..
This App must be installed to DEVICE MEMORY or it could have problems. Uninstall the Loader from Start, Settings, System, Remove Programs and reinstall to DEVICE MEMORY.
-----------------------------------------
-----------------------------------------
I Installed to Storage Card by mistake and now it wont uninstall:
In your File Manager browse to Device, Program Files and Delete the MSkip Android Tools folder
Next using a Registry Editor browse to HKLM, Software and Delete the MSkipAndroidLoader folder
Lastly try reinstalling the Cab to DEVICE MEMORY (it should let you now)
-----------------------------------------
-----------------------------------------
If you have read through this and still have problems then post your problem in the thread and you will be helped
Mark.
thanks very much!!! nice app!!! finally got our dual boot!!!
ty ty ty mskip
and welcome to HD Mini forums
Nice one, mskip! Thanks!
tzacapaca said:
ty ty ty mskip
and welcome to HD Mini forums
Click to expand...
Click to collapse
Thanks
Although I dont own an HD Mini I'm happy to help wherever I can.
Mark.
works well! thanks a lot!
That's looks like great!
mSkip, Thanks for you and Welcome to your brother HTC HD2, HTC HD Mini
Thnx for the app, sounds great!
Installation works perfect. I just got a non-signed error af
ter reboot (testing the boot menu) but guess that I will have better luck next boot.
-- edit --
problem continues, also while trying to start from the start menu (android softreset), settings from folder do work..
Problem here. i install it and it works, but not from the start. I have choose android as default operation system, but it always starts up first windows mobile, and then nothing happends. I mus then click on the android icon and then android started. is this correct?
superzuan said:
Problem here. i install it and it works, but not from the start. I have choose android as default operation system, but it always starts up first windows mobile, and then nothing happends. I mus then click on the android icon and then android started. is this correct?
Click to expand...
Click to collapse
So you have Android set as the default on boot up? Does it say Android is set as default when the screen pops up? What time out do you have set? Which folder do you have set?
Do you have a registry editor app on your phone so you can check some settings for me?
Mark.
I come back tomorrow im now going to sleep
Sent from my HTC Liberty using XDA App
superzuan said:
Problem here. i install it and it works, but not from the start. I have choose android as default operation system, but it always starts up first windows mobile, and then nothing happends. I mus then click on the android icon and then android started. is this correct?
Click to expand...
Click to collapse
i had similar problem
in fact the folder was not setup correctly.
i fixed this thanks to the app folder in start menu, redefine it to my sdcard root, it works perfectly now
after install this cab my hd mini stuck at win loading..
i already install this apps into device memory.. and i choose Android and softreset.. my phone going restart n stuck at wndow loading.. never get back in normal.. when its goin sleep mode i press power button just blank screen appear.. what should i do? plz help me... i never can use my phone right now cause this problem..
northman5208 said:
i already install this apps into device memory.. and i choose Android and softreset.. my phone going restart n stuck at wndow loading.. never get back in normal.. when its goin sleep mode i press power button just blank screen appear.. what should i do? plz help me... i never can use my phone right now cause this problem..
Click to expand...
Click to collapse
Please give us more details as it is doubtful your issue is related to this Android Loader v1.0 cab. For example, is it the same result if you manually select Haret_Photon7227.exe from SDCard and start Android? Is it the same issue if you boot into Windows Mobile?
If you have only just installed Android to your HD Mini, perhaps you use the manual method for a few times so there are no booting issues. Without knowing the full details it could simply be that your files zImage, initrd.gz, system.ext2, STARTUP.TXT, HARET_PHOTON7227.exe and the update directory are NOT installed in your SDCard root directory ie. (SDCard\)
Wowser said:
Please give us more details as it is doubtful your issue is related to this Android Loader v1.0 cab. For example, is it the same result if you manually select Haret_Photon7227.exe from SDCard and start Android? Is it the same issue if you boot into Windows Mobile?
If you have only just installed Android to your HD Mini, perhaps you use the manual method for a few times so there are no booting issues. Without knowing the full details it could simply be that your files zImage, initrd.gz, system.ext2, STARTUP.TXT, HARET_PHOTON7227.exe and the update directory are NOT installed in your SDCard root directory ie. (SDCard\)
Click to expand...
Click to collapse
i never have problem to boot Haret from sdcard before this... my hd mini working just fine in android... i been try not to make its in sleep mode, but my phone is not stop loading even after 2hour.. its look like my phone be very2 slowly...
This is unusual as Android Loader v1.0 cab does not change the ROM bootloader. it merely automates the process of having to go into the SDCard then selecting Haret_Photon7227.exe. Maybe you could try the solution that -rObin- applied in post #13 and that is to make sure that Android Loader v1.0 setting is physically selected as the sdcard\ ie. Storage Card root. To change this you need to go into the windows mobile start menu folder called Android Loader (as explained in post #1) then select the Manager application to change the default directory to "Storage Card" then press OK.
Otherwise if this still does not fix things, please uninstall Android Loader v1.0 cab so the associated Android Loader v1.0 cab HKLM settings can be removed as well as the software, then try manually selecting Haret_Photon7227.exe from \SDCard directory and start Android. Is the result the same?
Wowser said:
This is unusual as Android Loader v1.0 cab does not change the ROM bootloader. it merely automates the process of having to go into the SDCard then selecting Haret_Photon7227.exe. Maybe you could try the solution that -rObin- applied in post #12 and that is to make sure that Android Loader v1.0 setting is physically selected as the sdcard\ ie. Storage Card root. To change this you need to go into the windows mobile start menu folder called Android Loader (as explained in post #1) then select the Manager application to change the default directory to "Storage Card" then press OK.
Otherwise if this still does not fix things, please uninstall Android Loader v1.0 cab so the associated Android Loader v1.0 cab HKLM settings can be removed as well as the software, then try manually selecting Haret_Photon7227.exe from \SDCard directory and start Android. Is the result the same?
Click to expand...
Click to collapse
I just do hard reset to my phone.. n everthing going back to normal.. and i manually selecting haret my phone just transfroms to andriod without any problem.. i really want this apps in my phone but for now i so scare to install its again in phone memory.. anyway thank for helping me bro...
pietje63 said:
Thnx for the app, sounds great!
Installation works perfect. I just got a non-signed error af
ter reboot (testing the boot menu) but guess that I will have better luck next boot.
-- edit --
problem continues, also while trying to start from the start menu (android softreset), settings from folder do work..
Click to expand...
Click to collapse
Problem is most likely that I did not read the instructions and installed the app on SD. Uninstallation does unfortunately not work (hangs) and reinstallation is therefore impossible..
pietje63 said:
Uninstallation does unfortunately not work (hangs) and reinstallation is therefore impossible..
Click to expand...
Click to collapse
try uninstalll from ActiveSync on windows, maybe it would work better?
Tools > Add/remove programs
Hi all,
I am trying to make sense of how the android system is made up w.r.t to boot/kernel.
I have been looking at the .img files in the build (I built for the "passion" device), and have been googling around to find some more information about the various .img files.
I ran into a nice HOWTO in android-dls.com 's WIKI, titled HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images (I'm sorry, I'm a new user so XDA won't allow me to post links. I will try to modify my post a soon as I'm granted permission for that)
but I am afraid it is a little outdated:
I have several questions, but I will try to be brief, so I'll focus on
one of them, and if that works I'll proceed to the next questions, all related to "Android bringup for dummy embedded linux kernel experts".
I am fairly aware of differences between different linux
configurations, and I am very familiar with linux bringup concepts, so I will just use common examples from the linux world as my terminology. Hope it will be clear enough.
I understood that boot.img a combination of a kernel (e.g. bzImage in linux) and an initial ramdisk (e.g. initrd.gz), wrapped by some header, as in common linux kernel loading practice (piggy.o etc.).
Now, the aforementioned HOWTO says that the "recovery" image is built on
the same way, and that it is stored on the target's /system/
recovery.img .
I would assume that this would be compound of the ramdisk-
recovery.img, and some other kernel.
Now, the problem is that:
1. This /system/recovery.img does not exist from what I saw (on my
Motorola XOOM tablet)
2. What does exist is /system/boot-from-recovery.p , which is
created during the boot process in obj/PACKAGING/
recovery_patch_intermediates/recovery_from_boot.p .
I saw tons of posts referring to the files, all said that "in order to
replace the rescue disk image, this file needs to be renamed" - but I
am looking for a way to figure out what it is, and how to extract its
contents.
I assume /system/recovery.img is deprecated, is that correct?
3. I did not see any flash devices in /proc/mtd (which is strange).
I searched for hours before sending this post, so I would appreciate
your help. I also posted a similar message at the google android-building group, but it has not been answered yet, and I got the impression that these forums are more active and can help me get where I need.
If it is not the right place to ask the question please let me know -
I just assume this is a general android concept and not device
specific.
Thanks,
Ron
I meant of course /system/recovery-from-boot.p , and not recovery-from.boot.p
-R
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Well, it helped me. I'm new to rooting and just came across mention of this file. I am trying to learn 'why' as well as 'how'', so your post was informative.
Was going to ask a dumb question but I figured it out
i need to delet those files
bigrammy said:
Was going to ask a dumb question but I figured it out
Click to expand...
Click to collapse
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
recovery from boot p
ahmed morsy said:
Hello
can't delete those files >> i am rooted but every time i delete or rename it take permission then nothing happen >> how i can delete them plsssssssssssssssssssssssssssssssssssssss
Click to expand...
Click to collapse
Hey good day. Did you get your problem fixed...? I have an xt912 it has the same file. For days I've been trying to wipe the phone. Tryed rooting it. I tryed reprogramming it. And I got through with all of that. But everytime the phone boots up it goes back to the same state. Then I used a root browser and while exploring I saw this recovery from boot file. I need help. And I don't think I can downgrade the Motorola phones. Thanks in advance.
jman0 said:
Hi,
I don't know if you managed to find out what "recovery-from-boot.p" is, since this is quite an old post, but I think I'll try to help anyway.
recovery.img is not deprecated at all. From my own experience, it looks like "recovery-from-boot.p" is a protection measure introduced in Gingerbread, but not the recovery itself. What it does is replacing any recovery currently installed on the phone with the default one on every boot.
I discovered it after flashing a custom recovery on my Android 2.3.4 phone. It worked, but just during the first boot. The next time I rebooted the phone, the default recovery image was there again. After browsing several sites, I found that "recovery-from-boot.p" is responsible for that.
So, if you flash a custom recovery image on a Gingerbread phone and want to keep it forever, you must delete this "recovery-from-boot.p" from /system, or at least rename it. That way, your new custom recovery will never get overwritten buy the default one, unless you do it yourself.
I hope this helps you and clarifies this question.
Click to expand...
Click to collapse
i have deleted it . then flash recovery ,, but it failed .. it wont even now go to stock recovery itself.. any help..
Does recovery from boot has to do anything with ota update applying ? or it will cause issues in system update ?
I have recovery-from-boot.p in my system and i cant root my phone i cant change the recovery img ... Help?
I hadn't had to deal with this for some time, perhaps because I've updated my devices (Nexus 4, Nexus 5, Nexus 7 '13) with the factory images, with "-w" removed from flash-all, then flashing CWM's recovery, ensure SuperSU was installed, then continuing. Today, I used the new OTA image on my Hammerhead/N5, and recovery-from-boot.p seems to be up to its old tricks again.
Solution is simple.
Flash your alternate Recovery in fastboot, fastboot flash recovery [recovery image file] . Boot into Recovery. Apply/install root app (typically via sideload). Mount /system. adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak. Reboot. Done. (If you're unfamiliar with fastboot, adb, and flashing new recovery partitions, you have some reading to do. Commence RTFM.)
I also used to have to move /system/etc/install-recovery.sh but that seems to be gone in Marshmallow. :} Or moved...?
well, after following a guide I have extracted the system.img from a pure-nexus ROM(The ROM I'm currently using), now I can see that "recovery-from-boot.p" file is responsible for recovery lock in my phone. I'll keep it short and straight to the question
"Can I remove this file and rebuild the .dat file and flash it?, so that I won't have any other problems at all"
I want to know if recovery-from-boot.p file is linked to anything other than just locking the recovery or re-flashing it innumerable times.
anyone know how to get into the system and change any file in there with access to computers without enabling usb debug on android phone ??
ycusoy said:
anyone know how to get into the system and change any file in there with access to computers without enabling usb debug on android phone ??
Click to expand...
Click to collapse
Are you on stock rom or a rooted one? It is possible through recovery. In CWM and 4EXT recoveries, there's an option to mount system. Then you should be able to access it from a pc. In recovery you dont have the ADB option so I guess it'll work. If you're not rooted and do not have custom recovery installed, I don't know. You might also try QtADB program, is like a file explorer on your pc with which you can access phone files in a graphical manner, without need to know ADB commands. You need to have Android SDK installed on your pc for these methods to work
Sent from nowhere over the air...
Rapier said:
Are you on stock rom or a rooted one? It is possible through recovery. In CWM and 4EXT recoveries, there's an option to mount system. Then you should be able to access it from a pc. In recovery you dont have the ADB option so I guess it'll work. If you're not rooted and do not have custom recovery installed, I don't know. You might also try QtADB program, is like a file explorer on your pc with which you can access phone files in a graphical manner, without need to know ADB commands. You need to have Android SDK installed on your pc for these methods to work
Sent from nowhere over the air...
Click to expand...
Click to collapse
hmm .. that's my fault. I forgot to backup the data from the phone. There are two mistakes here that I made:
A. I tried upgrading my android phone to a higher level, but the one included with the correct phone model in the / system / build.prop.
2. I also already remove the formal application in the directory / sytem / app.
therefore, I want to ask if there are other ways that I can use to get to the root without interference adb.exe? for example with special commands in windows or ubuntu, or by flashing using a particular application, or the fastboot command which allows root can be accessed with ease ..
ycusoy said:
hmm .. that's my fault. I forgot to backup the data from the phone. There are two mistakes here that I made:
A. I tried upgrading my android phone to a higher level, but the one included with the correct phone model in the / system / build.prop.
2. I also already remove the formal application in the directory / sytem / app.
therefore, I want to ask if there are other ways that I can use to get to the root without interference adb.exe? for example with special commands in windows or ubuntu, or by flashing using a particular application, or the fastboot command which allows root can be accessed with ease ..
Click to expand...
Click to collapse
Ok... But you can still enter in recovery right? I mean, don't know exactly what phone model you have, but there's power on key combination that usualy allow to boot in recovery. For ex, on Desire S I keep pressed vol-down+ power then select recovery. And from there I can acces system or flash another ROM. You cannot do the same?
Sent from nowhere over the air...
Rapier said:
Ok... But you can still enter in recovery right? I mean, don't know exactly what phone model you have, but there's power on key combination that usualy allow to boot in recovery. For ex, on Desire S I keep pressed vol-down+ power then select recovery. And from there I can acces system or flash another ROM. You cannot do the same?
Sent from nowhere over the air...
Click to expand...
Click to collapse
yup ... It is true bro. I can still access the recovery mode. rom to install it but I always fail. My cell phone specs, Nexian nx-a892. congenital previous 2.2.1 version, then I tried upgrading to 2.2.2 from GSmart G1315 product. Here I make text editing the wrong file build.prop. I change only the G1315 model only, without including the GSmart. Then came the refusal every time I go in recovery mode.
Various tools have been tried, but all to no avail. One way that I think can be done only with fastboot. But until this moment I have not managed to solve the secret of accessing the android system, without the ADB and USB Debug ...
At other times, I had also tried the Linux operating system. Because Android applying the same thinking with linux. but just the same, I stopped in there a way to access the root ...
ycusoy said:
yup ... It is true bro. I can still access the recovery mode. rom to install it but I always fail. My cell phone specs, Nexian nx-a892. congenital previous 2.2.1 version, then I tried upgrading to 2.2.2 from GSmart G1315 product. Here I make text editing the wrong file build.prop. I change only the G1315 model only, without including the GSmart. Then came the refusal every time I go in recovery mode.
Various tools have been tried, but all to no avail. One way that I think can be done only with fastboot. But until this moment I have not managed to solve the secret of accessing the android system, without the ADB and USB Debug ...
At other times, I had also tried the Linux operating system. Because Android applying the same thinking with linux. but just the same, I stopped in there a way to access the root ...
Click to expand...
Click to collapse
anyone can help me ???????:crying::crying::crying::crying::crying::crying::crying::crying::crying:
I'm having the same problem. Can anyone help accessing files on a soft-brick with android stock rom, with USB debugging disabled?
MyTab brick
And what if I have also softbricked tab (Mytab 10 dual core) I have messed up with build.prop file probably but I don't have any bootloader mode or any option like that. Is there any way to get to the Android system files? I have now sent it for a warranty however I'm sure they won't accept it. Tab launches but hungs at boot screen (computer can see it). I have USB debugging off. Any help would be apreciated much
I have a Spreadtrum based S930 phone.
It's on a boot-loop and the only thing working is the recovery mode. (While I was playing around with it, I noticed that it had a fastboot partition but, I never found a way to access it - only has 4 buttons: POWER, UPVOL, DWNVOL, and HOME.)
I tried to install an app in ZIP but, I got an error saying that it wasn't verified so I tried to manually install it by unpacking it directly into the folders. After doing so, it still didn't work AND the equalizer app that I installed began not to work either. I then tried to manually uninstall it by deleting the files. It didn't work (or at least my equalizer app still didn't work) so, I tried to restore it to the way it was. I deleted the BIN, ETC, and LIB folders and was replacing them with the ones I originally had before the installation but the phone suddenly rebooted. Hence, now it's on a boot-loop.
I can still go into recovery-mode but I can't use adb shell commands because it says that it can't find it (/SYSTEM/BIN/SH). I tried to push it but I get an error saying that I don't have access/permissions for it.
Before it happened, I was able to extract a boot.img but I can't get it in because...
...I don't have access to fastboot and adb shell options.
...I tried creating my own ROM but I get signing issues.
The only thing that seems to work is the push and pull adb commands (remount, logcat, and bugreport gives me an error) and anything I push doesn't stay there when the phone reboots. In recovery-mode, the phone only stays on for about 10 minutes before it restarts.
I've tried pulling some files. The RES folder seems to be intact. BIN and ETC still have some files in them but, the SYSTEM files are completely gone.
Any input would be very much appreciated.
To do list:
- figure out a way to do boot using the SD card
- install a new kernel
Hindrances:
- phone does not even recharge the battery; it simply enters the boot-loop mode
I'm obviously an android noob but I can follow directions and think of a way to piece things up from different sources. I just need someone to point me in the right direction.
...or is this a hopeless case?!
I'll try to keep it short and keep a clear overview.
I rooted my Nexus 5 with the Towelroot app. Everything went perfectly fine (I had to do a recovery, but after that, Nexus running smooth and it was rooted.
Then I decided to try something stupid. Alter the Nfcnci.apk so that the NFC TAG scanning app was silent instead of the end.ogg noise when scanning a NFC tag.
It all went wrong when I merged the unpacked .apk files back into a .rar and convert it to a .apk with "formatter" program.
When I tried to put the NfcNci.apk app back in the system/app folder with authorisation 664 it didn't work anymore. the stock app crashed.
The nfc part of my phone wasn't working anymore ! (when opening NFC tools, i got a NFC ERROR message... apparently, i did something wrong when trying to replace the app with my modded version)
So i did the most stupid thing I could have done: instead of putting the original NfcNci.apk file back into the system/app folder I did a hard reset recovery (go into Recovery mode, wipe data)............
Now, with my freshly recovered nexus 5..... I CAN'T GO INTO SETTINGS to turn on USB debugging (because I clearly wanted to put the original 4.4.3 image back on my phone)
so i'm stuck with a phone that :
1) is rooted.
2) doesn't go into settings so I can't turn on USB debugging
3) doesn't go onto the app store because i can't link my google account because i can't go into Settings.
4) is actualy a dumbphone now. The only thing I can do is use stock apps and call and text someone.
Could someone PLEASE put me out of my misery?
i'm litteraly crying here. I had this phone for 2 weeks.....
I want to unroot the damn thing and go back to the way it was....
Best regards,
Tom
1) questions go into the Q&A forum.
2) you shouldnt mod stuff when you're not sure what you are doing
3) factory reset in recovery does not fix any mods you have made to /system, it only wipes data.
4) follow this to go back to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Fastboot doesn't need usb debugging on. Flash the stock files with fasboot. You will get back to stock but ur data will get erase.
or simply just flash the system.img which won't erase ur data
Code:
fastboot flash system system.img
varuntis1993 said:
Fastboot doesn't need usb debugging on. Flash the stock files with fasboot. You will get back to stock but ur data will get erase.
or simply just flash the system.img which won't erase ur data
Code:
fastboot flash system system.img
Click to expand...
Click to collapse
Yup, just pull the stock factory image from Google developers website and unpack it. Put system.img into your fastboot directory. Use CMD (assuming you're on Windows) and CD to that location and fastboot flash system system.img, like he said.
If you have trouble with fastboot follow the first link given to you.
thanks
Thank you all very much for your help.
I managed to put the stock img back to my phone.
the problem was that my phone wasn't unlocked, therefore I couldn't enter the fastboot command lines.
Phone is back to stock 4.4.3.
@Zepius you are right, you shouldn't mod stuff if you don't know what you are doing, but you do have to go through a learning process... you also had to do it for the first time once, right?
I think my big mistake was, not to follow the amazing guides here in XDA on how to root, change apk's etc etc...
one more question. IF you take a stock app (NfcNci.apk) do you have to sign it to be able to get it to work?
All i wanted to do was unpack the apk, change a sound file and repack it so that the darn NFC tag doesn't make that sound when I scan a tag, waking up my wife when i put it to sleep mode...
well, guess i'll hang the tag somewhere outside of our room
again, thank you all for your help and not bashing me.
Tom
tom_el_camino said:
I think my big mistake was, not to follow the amazing guides here in XDA on how to root, change apk's etc etc...
one more question. IF you take a stock app (NfcNci.apk) do you have to sign it to be able to get it to work?
Click to expand...
Click to collapse
Don't sign system apps, just take the AndroidManifest.xml and META-INF folder out of the original .apk, open the modified one with 7zip or your alternative and paste it in.